Docker Utils: Utility method to create file in container #12122
Merged
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
2357648 to
1cd6500
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Adds a utility method to create a file in the docker container, by just passing the content of the file. I find myself reusing the same approach quite often, so IMO it would be much nicer to have it available as a utility.
Permissions
When running this inside a container, the file will be created by the
rootuser. If the target container runs it's process as a custom (non-root) user, it may not have access to files created byroot.The additional
chmod_modeargument can be used to ensure the file is available to the custom user. (We could presumably alsochownthe file to the same effect, but I only usedchmodso far to make files available in this scenario.)