| 2023-01-13 17:28:27 |
Tiago Nobrega |
description |
The setup is this: a fedora 35 host (a google vm running a spread test), running an ubuntu 22.04 lxd instance, running snapd inside.
The behavior seems to be that a "snap set ..." command will fail the first time, and then work.
The failure output is this:
root@test-ubuntu2204:~# snap set system refresh.hold=2023-01-14T19:38:14.031694Z
error: cannot perform the following tasks:
- Run configure hook of "core" snap (run hook "configure": cannot load apparmor profiles: exit status 1
apparmor_parser output:
Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
Use --subdomainfs to override.
)
... then if I repeat the command it works fine. Confirmed to happen in Fedora 35 and 37 so far. The attached file has the commands used to reproduce it together with more debugging info. |
The setup is this: a fedora 35 host (a google vm running a spread test), running an ubuntu 22.04 lxd instance, running snapd inside.
The behavior seems to be that a "snap set ..." command will fail the first time, and then work.
The failure output is this:
root@test-ubuntu2204:~# snap set system refresh.hold=2023-01-14T19:38:14.031694Z
error: cannot perform the following tasks:
- Run configure hook of "core" snap (run hook "configure": cannot load apparmor profiles: exit status 1
apparmor_parser output:
Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Warning: unable to find a suitable fs in /proc/mounts, is it mounted?
Use --subdomainfs to override.
)
... then if I repeat the command it works fine. Confirmed to happen in Fedora 35 and 37 so far. The attached file has the commands used to reproduce it together with more debugging info. The file shows that this behavior happens with snapd 2.58, but not with 2.57.6. |
|
