-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[CI:DOCS] Fix documentation on read-only-tmpfs #16374
Conversation
@edsantiago PTAL |
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.
LGTM apart from the one-long-line format; I won't block over that. Thank you.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago, rhatdan 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 |
This protects the container's image from modification. Read-only containers may | ||
still need to write temporary data. The best way to handle this is to mount | ||
tmpfs directories on _/run_ and _/tmp_. | ||
This protects the container's image from modification. By default read-only containers can write to temporary data. Podman mounts a tmpfs on /run and /tmp within the container. If the container should not write to any file system within the container, including tmpfs, set --read-only-tmpfs=false. |
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.
On second thought, though, you might want to backtick the paths, and asteriskize the option.
Signed-off-by: Daniel J Walsh <[email protected]>
LGTM, but documentation-focused reviewers may still want the double asterisks on the |
@TomSweeneyRedHat PTAL |
/lgtm |
/hold cancel |
Signed-off-by: Daniel J Walsh [email protected]
Does this PR introduce a user-facing change?