-
Notifications
You must be signed in to change notification settings - Fork 846
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
systemd
doesn't mount /
as shared
#8922
Comments
Yep, looking at the current code (the link in the discussion points to an older release), the root filesystem should be automatically remounted as shared by systemd, but it isn't because systemd is running in container mode. See here: https://cgit.freedesktop.org/systemd/systemd/tree/src/core/mount-setup.c#n383 (Since this is the same root cause as #8840 , it might be worth asking if systemd needs to run in container mode under WSL? To the best of my knowledge, none of the pre-native-support systemd hacks used container mode, and systemd-detect-virt still picked up that it was running under WSL just fine.) |
Well, guess I didn't need to rush that fix into bottle-imp 0.8 after all... 😀 |
Still present under 0.68.4. |
This is a pretty annoying issue, as if you run Kubernetes with root mount propagation (for example Prometheus root exporter), it will not work out of the box. Same goes for Nvidia GPU Operator which some of the driver installer required host path mount to detect existing Nvidia drivers. |
May I know if there is any update regarding this ticket? |
I am on opensuse leap 15.5 and I am also experiencing this issue. |
Revisited this issue as it still persists in WSL 2.0.9
|
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Version
Windows version: 10.0.22621.521
WSL Version
Kernel Version
5.15.62.1-microsoft-standard-WSL2
Distro Version
ArchWSL
Other Software
Repro Steps
systemd
support [1]wsl --shutdown
,wsl
podman images
Expected Behavior
Podman run without warning and error.
Actual Behavior
Podman print a warning regarding shared mount.
❯ podman images WARN[0000] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers
Diagnostic Logs
This has been an issue for a while. However, back then there is still no native WSL's
systemd
support. The introduction of nativesystemd
support made me revisit this issue, and found that it is still persist.Current workaround is by using WSL's boot command in
wsl.conf
. [1]The text was updated successfully, but these errors were encountered: