-
Notifications
You must be signed in to change notification settings - Fork 3.8k
blockfile: Ensure required options are always set #12065
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
blockfile: Ensure required options are always set #12065
Conversation
|
Hi @fidencio. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
247f171 to
a7c7478
Compare
a7c7478 to
6408813
Compare
|
/ok-to-test |
When using blockfile snapshotter and passing specific filesystem mount options, the users may be caught by surprise by the fact that some options are required but not documented anywhere. The easiest way to solve this is by ensuring that the "loop" required option is always added to the mount options. Signed-off-by: Fabiano Fidêncio <fidencio@northflank.com>
6408813 to
e0d733c
Compare
|
/retest |
…s-part-of-the-mount-options blockfile: Ensure required options are always set
When using blockfile snapshotter and passing specific filesystem mount options, the users may be caught by surprise by the fact that some options are required but not documented anywhere.
The easiest way to solve this is by ensuring that the "loop" required option is always added to the mount options.