Julian Gilbey <j...@debian.org> wrote on 15/05/2023 at 22:05:37+0200:
> On Mon, May 15, 2023 at 10:37:32AM +0100, Julian Gilbey wrote: >> [...] >> But now we're back to the original problem cgfsng problem (running >> with --logpriority TRACE): >> >> lxc-start debian-sid 20230515092650.376 WARN cgfsng - >> ../src/lxc/cgroups/cgfsng.c:get_hierarchy:149 - There is no useable devices >> controller >> lxc-start debian-sid 20230515092650.376 ERROR cgfsng - >> ../src/lxc/cgroups/cgfsng.c:cg_legacy_set_data:3098 - No such file >> or directory - Failed to setup limits for the "devices" >> controller. The controller seems to be unused by "cgfsng" cgroup >> driver or not enabled on the cgroup hierarchy >> lxc-start debian-sid 20230515092650.376 ERROR cgfsng - >> ../src/lxc/cgroups/cgfsng.c:cgfsng_setup_limits_legacy:3165 - No such file >> or directory - Failed to set "devices.deny" to "a" >> lxc-start debian-sid 20230515092650.376 ERROR start - >> ../src/lxc/start.c:lxc_spawn:1893 - Failed to setup legacy device cgroup >> controller limits > > Ah, success! I followed the recipe on > https://wiki.debian.org/LXC/CGroupV2 referenced in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944389 (adding the > lines > > lxc.cgroup.devices.allow = > lxc.cgroup.devices.deny = > > to the end of /var/lib/lxc/debian-sid/config) and it now works. > > But there's no mention of this in /usr/share/doc/lxc/README.Debian.gz, > and I don't need to do this on my other machine, so there's still > something weird going on on this machine. Perhaps it's a hardware > thing? > > Oh joys! > > Best wishes, Ah, I don't remember seeing these logs before, maybe I forgot to ask for a full trace, sorry. Do you see anything in /var/log/audit or /var/log/syslog or /var/log/kern.log about apparmor denies? Cheers, -- PEB
signature.asc
Description: PGP signature
