Pass file secrets to "podman build" via parameter "--secret" #777
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.
Dear maintainers!
At the moment podman-compose always passes file secrets to podman as a
--volume
option, both when starting containers and when building images.I propose that file secrets for building are instead passed as a
--secret
option. This would make them available forRUN --mount=type=secret…
instructions and would improve compatibility with docker-compose.Example
To build directly from this Dockerfile one has to supply the secret like this:
podman build --secret=id=my_secret,src=./my_secret .
Building from the docker-compose.yaml with
podman-compose build my-service
should produce the same results as thepodman build …
command above.Yours sincerely
wiehe