-
Notifications
You must be signed in to change notification settings - Fork 245
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 setting mountopt for vfs driver #1972
Comments
I don't see how this is our issue. Other then saying don't do that. |
Is there some inherent reason why users should be able to set |
VFS file systems are not mounted. |
it should be possible to specify nosuid,noexec,nodev for a bind mount, so in theory we could "mount" a vfs on itself using a bind mount and specify these options. We could do it only for the cases where it is needed, as in this case
It is a low priority feature, and likely our team won't work on it any time soon, @legobeat interested in opening a PR? |
Feature request description
Rootless podman-in-podman, or sudo in rootless, are not working in rootless mode on
vfs
due to the root filesystem mount being mounted withnosuid
set:Trying to set
storage.options.vfs.mountopt = "suid"
is not recognized, as expected from reading docs:Suggest potential solution
Exposing
mountopt
forvfs
driver just like foroverlay
would allow unlocking by setting appropriate mountopt.Have you considered any alternatives?
Using
overlay
instead ofvfs
unfortunately does not work as it results in incorrect ownership in rootless: containers/podman#22810 (comment)Additional context
Related
The text was updated successfully, but these errors were encountered: