-
Notifications
You must be signed in to change notification settings - Fork 789
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
Document more buildah build --secret options #5784
Conversation
/retitle Document more buildah build --secret options |
Ephemeral COPR build failed. @containers/packit-build please check. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR looks good to me, but should changes in parse.go
go in seperate commit ? Not sure.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, nalind The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
||
To later use the secret, use the --mount flag in a `RUN` instruction within a `Containerfile`: | ||
|
||
`RUN --mount=type=secret,id=mysecret cat /run/secrets/mysecret` | ||
|
||
Note: Changing the contents of secret files will not trigger a rebuild of layers that use said secrets. | ||
The location of the secret in the container can be overridden using the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about an example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added one.
759059a
to
af1fe4e
Compare
Describe the "env" and "type" options in the buildah-build(1) man page. When parsing the "--secret=" flag for the CLI, instead of ignoring an option that we don't recognize, return an error. Even though the set of meaningful "id" values for secrets is passed in via the command line, don't directly use it to construct a file path. Change the default mode for SSH agent sockets that we create from 0o620 to 0o600. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
/lgtm |
What type of PR is this?
/kind documentation
/kind other
What this PR does / why we need it:
How to verify it
Updated test to verify that we complain about unrecognized
--secret=
options!Which issue(s) this PR fixes:
Resolves #5282, or at least points people in the right direction.
Special notes for your reviewer:
Does this PR introduce a user-facing change?