Use a non-root user within the preparer container #32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Note to self: make sure this doesn't bust the local client. |
smashwilson
added a commit
that referenced
this pull request
Jan 29, 2016
Use a non-root user within the preparer container
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bump to the latest Alpine image. Create and use a non-root user for the preparer container.
Kind of a hack: the
dockeruser within thedocker-machineVM has UID 1000 and owns all files within volume-mounted directories. I'm using the same UID for the preparer user so thatdocker run -vstill works (and therefore the local client).