Added support to define custom context directory instead of '.' (is still default when omitted) #97
Conversation
This file contains 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
|
Hi @JimPanse81, My apologies for the delay in response. I have been extremely busy in the past few months. I will review and merge your contributions this week. Thanks again for your PR. It is greatly appreciated :-) |
|
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.
In Version 1.18.0 there is no possibility to define a custom context directory. The context is appended hard coded as '.' at the end of the build command (method 'PodmanBuildCommand.build()'). Especially when copying files from the host into the image it is often necessary to expand the context to a higher directory.
This change adds the build configuration option "contextDir". If the option is ommited the fallback is still '.'