-
Notifications
You must be signed in to change notification settings - Fork 220
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 loses MS_RDONLY when remounting bind mount of a read-only source #282
Comments
This error does not occur on Fedora 31 Workstation with
toolbox is working fine there but not on Silverblue 31. |
I seem to have the same issue. Versions in use:
|
This issue continues to exist in |
Same error in Fedora Silverblue 31 (fresh installation, build 31.20191001.n.0, basecommit f343f95c7a94865c6d490b11286f99e3e47bad3aa7bcb254d3f3451ea705157e) with crun-0.10-1.fc31.x86_64 and podman-1.6.1-2.fc31.x86_64 overriden. |
I've also encountered this issue. The I came across the Silverblue project recently and was really interested to try it out. Toolbox seems quite crucial for its functioning so I've been trying to work out what the problem is. My system is at Fedora 31 also:
|
I've tried to make it run on at least F30. Still broken.
Upgrading to 1.6.1 (f30 build can be found in koji) will get you the same error, as in issue. There is also a build for f29 available. And it will eventually be pushed to main repository... This means, toolbox will be broken everywhere. |
Let's only focus on this error in this issue which occurs on Fedora 31 Silverblue:
It's now fixed by containers/crun#120 |
@nexfwall that's something else. I'd suggest filing a separate issue for it. |
@debarshiray no need, I think, because it's from 1.5.1 (outdated). 1.6.1 is built for all supported versions of Fedora and will be pushed eventually. |
This error has been occurring for a while in Fedora 31 Silverblue with podman-1.6.0-dev.
Now also still with podman-1.6.0:
Since coretoolbox works for me now in SB31 this looks like it could be a toolbox issue so I am filing this report.
The text was updated successfully, but these errors were encountered: