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
User namespace remapping doesn't work with multi-stage builds #392
Comments
Thanks @shaneog, this is a tricky one! 🤔 |
From the moby issue, might that be viable in your case @shaneog? |
I've disabled user namespace remapping for now, and I'm using the permission scripts to fix any file ownership issues. |
We've brought back |
I'm going to re-open this one, as it's still an issue when user namespace remapping is turned on. |
Looks like it's still an issue in the latest buildkite/elastic-ci-stack-for-aws with default configuration? |
(for some reason upgrading the stack from v3.2.1 to v4.2.0 has triggered this issue for us, even though v3.2.0 seems to be where |
((ah — we had |
Yup, still an issue @pda. |
👀 |
User namespace remapping doesn't work when you use multi-stage builds such as with the below Dockerfile.
Is this possible to fix, or am I stuck with using user namespace remapping OR multi-stage builds?
References:
moby/moby#34645
buildkite/agent#407
Example Repo: https://github.com/shaneog/bk-issue-392
Error:
Dockerfile:
Using Buildkite stack v2.3.5
The stack was created with all default values, except for the agent token, and enabling "User namespace remapping"
The text was updated successfully, but these errors were encountered: