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
"udevadm trigger" fails in containers with ro /sys #14060
Comments
@keszybz |
I figure we should just exit early in udevadm trigger when we detect we are run in a container |
Fixes systemd#14060. (cherry picked from commit dc11d2b)
88da55e commit reverted required change.
Ubuntu's netplan fails to run inside systemd-nspawn container: $ netplan apply
host0: Failed to write 'change' to '/sys/devices/virtual/net/host0/uevent': Read-only file system
subprocess.CalledProcessError: Command '['udevadm', 'trigger', '--attr-match=subsystem=net']' returned non-zero exit status 1. |
I am having the same issue on Debian. It's a systemd issue. |
systemd version the issue has been seen with
v243
Used distribution
Debian sid
Filed as downstream bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944860
Since v243,
udevadm trigger
fails in a container with read-only /sys. I tested both LXC and systemd-nspawn:v242:
v243:
This is a result of commit 97afc03
@keszybz this change in behaviour is problematic, as we now have packages failing to install inside containers. We have quite a few packages which ship udev rules and trigger udev after installation.
The text was updated successfully, but these errors were encountered: