-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jenkins/cloud: Stop binding /srv, use workspace #211
Conversation
See bwrap issue 284 for where I got on the unprivileged bits. |
Just use $WORKSPACE for the images - it'll be naturally namespaced by our job and lifecycled with it. Note I tried *really* really hard to also drop `--privileged` but the problem is the usage of bwrap drags us into unprivileged nested containers. One downside is we'll be rsyncing in the images on each job invocation, but I'll work on a fix for that later.
Rebased 🏄♂️ |
Yeah, that will mean a massive amount of data to rsync on each run. May I suggest until we fix that, we drop the workspace cleanup here? |
One approach we could take would be to do pruning (and s3 sync) as a separate task. So we drop the Does that sound OK? |
That makes sense, though... is it possible to do the symlink swap without having to |
@cgwalters: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We shouldn't `rsync` to the shared `/srv` location. Just sync directly to our `WORKSPACE` to avoid races. See also openshift#211.
We shouldn't `rsync` to the shared `/srv` location. Just sync directly to our `WORKSPACE` to avoid races. See also openshift#211.
Just use $WORKSPACE for the images - it'll be naturally namespaced
by our job and lifecycled with it.
Note I tried really really hard to also drop
--privileged
butthe problem is the usage of bwrap drags us into unprivileged
nested containers.
One downside is we'll be rsyncing in the images on each job
invocation, but I'll work on a fix for that later.