[SRU] 2.68.5: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2098137 [ Impact ] Error containing "cannot reload udev rules: exit status X" when doing an actions e.g. installation of hello-world on a privileged container. [ Test Plan ] 1. Produce error with snapd 2.67.1+25.04 deb (inside the lxd container) snap install lxd --channel=5.21/stable lxd init (use defaults) lxc launch -c security.privileged=true ubuntu:24.04 test lxc exec test -- bash snap install hello-world expect to see error ``` error: cannot perform the following tasks: - Setup snap "snapd" (24792) security profiles (cannot reload udev rules: exit status 1 udev output: Failed to send reload request: No such file or directory ) ``` 2. Change to snapd 2.68.5 deb (inside the lxd container) lxc exec test -- bash Moify /etc/apt/sources.list.d/ubuntu.sources: add <release>-proposed sudo apt update apt install snapd=2.68.5+ubuntu<release>.<iteration> e.g. apt install snapd=2.68.5+ubuntu25.04.2 snap install hello-world do not expect to see the error anymore ``` snap install hello-world 2025-08-01T18:49:01Z INFO Waiting for automatic snapd restart... hello-world 6.4 from Canonical✓ installed ``` Repeat for all targeted Ubuntu releases. ---original--- I think this is possibly a known issue since there's evidence of a workaround in e.g. https://stgraber.org/2017/01/13/kubernetes-inside-lxd/, but I couldn't find any proper discussion of it. Installing snaps in a privileged LXD container fails. Here's a test script:   $ lxc launch -c security.privileged=true ubuntu:16.04 snap-test   $ lxc exec snap-test apt update   $ lxc exec snap-test apt install squashfuse   $ lxc exec snap-test snap install hello-world   2017-08-24T12:03:59Z INFO cannot auto connect core:core-support-plug to core:core-support: (slot auto-connection), existing connection state "core:core-support-plug core:core-support" in the way   error: cannot perform the following tasks:   - Setup snap "core" (2462) security profiles (cannot setup udev for snap "core": cannot reload udev rules: exit status 2   udev output:   )   - Setup snap "core" (2462) security profiles (cannot reload udev rules: exit status 2   udev output:   ) This is because /sys is mounted read-only in privileged containers (presumably to avoid causing havoc to the host) and so the systemd-udevd service isn't started. The prevailing recommendation seems to be to work around it by making /usr/local/bin/udevadm be a symlink to /bin/true, but this looks like a hack rather than a proper fix.