-
Notifications
You must be signed in to change notification settings - Fork 443
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
Defining a user in multi-stage builds #1195
Labels
Comments
The errors produces are a list of chmod failures
|
Thanks for the detailed report 👍 I guess running the @eed3si9n any objections? |
That makes sense. |
eed3si9n
added a commit
to eed3si9n/sbt-native-packager
that referenced
this issue
Jan 25, 2019
Fixes sbt#1195 Since the user of the fabric8 image is already non-root, stage0 fails with ``` chmod: changing permissions of '/opt/docker': Operation not permitted ``` This switches the stage0 user to root explicitly so we can run `chmod` in there. In the actual image the user is set back to 1001.
Pull request here - #1197 |
muuki88
pushed a commit
that referenced
this issue
Jan 28, 2019
Fixes #1195 Since the user of the fabric8 image is already non-root, stage0 fails with ``` chmod: changing permissions of '/opt/docker': Operation not permitted ``` This switches the stage0 user to root explicitly so we can run `chmod` in there. In the actual image the user is set back to 1001.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using v1.3.16 and the multi-stage feature from #1190
The first stage of the multi-stage build may not have adequate rights to perform the
chmod
if the base image was already using an unprivileged user.You should be able to reproduce this using something like
Which produces a first stage of
User of the fabric8 image is already non-root
Could specify a user via configuration, or perhaps the first stage can safely be switched to
USER root
?The text was updated successfully, but these errors were encountered: