-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Allow --ro=[true|false] with mount flag #3738
Allow --ro=[true|false] with mount flag #3738
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mheon 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 |
lint's not happy @mheon |
pkg/spec/storage.go
Outdated
newMount.Options = append(newMount.Options, "ro") | ||
} | ||
default: | ||
return newMount, errors.Wrapf(optionArgError, "%s must be set to true or false, instead got %q", kv[0], kv[1]) |
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.
consider: s/instead got/instead received/
The 'podman run --mount' flag previously allowed the 'ro' option to be specified, but was missing the ability to set it to a bool (as is allowed by docker). Add that. While we're at it, allow setting 'rw' explicitly as well. Fixes containers#2980 Signed-off-by: Matthew Heon <matthew.heon@pm.me>
@rhatdan @baude @vrothberg @TomSweeneyRedHat @giuseppe This is green, PTAL |
LGTM |
1 similar comment
LGTM |
/lgtm |
The 'podman run --mount' flag previously allowed the 'ro' option to be specified, but was missing the ability to set it to a bool (as is allowed by docker). Add that. While we're at it, allow setting 'rw' explicitly as well.
Fixes #2980