-
Notifications
You must be signed in to change notification settings - Fork 321
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
crun 0.18 leaking mount options when it shouldn't #639
Comments
I am still in the process of trying to reproduce locally (my first attempt on F34 worked fine). What is the output you get from the last command? EDIT: nevermind my question... |
I am still not able to reproduce unless I modify the first container with: Can you show me the output of If the source bind mount has It could help to run |
it is useful to reset flags like nodev,noexec,nosuid if they are not specified in the bind mount itself. Closes: containers#639 Signed-off-by: Giuseppe Scrivano <[email protected]>
tentative fix: #640 marked as a draft as I need to test it better |
Ya, I'm not able to repro. on F34beta either, only F33.
So ya, that does appear to be the case. Though this is a test that's newly failing on F33, it wasn't failing until we updated packages. |
This seems like it will resolve the issue. I cloned the repo, checked out your PR, built crun and copied it to
|
it is useful to reset flags like nodev,noexec,nosuid if they are not specified in the bind mount itself. Closes: containers#639 Signed-off-by: Giuseppe Scrivano <[email protected]>
After building fresh VM images for podman CI, I'm seeing a unique failure @mheon thinks is coming from an updated crun package:
crun-0.18-4.fc33.x86_64
. We only see this failure when running podman-in-podman. The test passes fine when run simply on the host.I am able to reproduce this manually similar to the test, starting on a F33 VM as root:
According to the test code, this should not be finding
nodev
- but it does.The same reproducer when run on Ubuntu 20.04 VM and containers (using runc) does not reproduce the issue:
The text was updated successfully, but these errors were encountered: