AppArmor problem? Not sure

Hi sheepish smile

In advance, thank you so much for your time! Here’s my Linux release:

PRETTY_NAME=“Debian GNU/Linux 12 (bookworm)”

NAME=“Debian GNU/Linux”

VERSION_ID=“12”

VERSION=“12 (bookworm)”

VERSION_CODENAME=bookworm

ID=debian

And here is my snap version:

snap 2.57.6-1+b5

snapd 2.57.6-1+b5

series 16

debian 12

kernel 6.6.30-02726-gb84bbdf6955e

And here is my debugging info:

Oct 21 23:21:27 penguin systemd[1]: Starting snapd.service - Snap Daemon…

Oct 21 23:21:27 penguin snapd[1912]: AppArmor status: apparmor not enabled Oct 21 23:21:27 penguin snapd[1912]: overlord.go:263: Acquiring state lock file

Oct 21 23:21:27 penguin snapd[1912]: overlord.go:268: Acquired state lock file

Oct 21 23:21:27 penguin snapd[1912]: daemon.go:247: started snapd/2.57.6-1+b5 (series 16; classic; devmode) debian/12 (amd64) linux/6.6.30-02726-gb84bbdf6955.

Oct 21 23:21:27 penguin snapd[1912]: main.go:129: system does not fully support snapd: cannot mount squashfs image using “squashfs”: mount: /tmp/syscheck-mountpoint-4187126542: mount failed: Operation not permitted.

Oct 21 23:21:27 penguin snapd[1912]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)

Oct 21 23:21:27 penguin snapd[1912]: helpers.go:147: error trying to compare the snap system key: system-key missing on disk

Oct 21 23:21:27 penguin systemd[1]: Started snapd.service - Snap Daemon.

Oct 21 23:21:32 penguin snapd[1912]: daemon.go:521: gracefully waiting for running hooks

Oct 21 23:21:32 penguin snapd[1912]: daemon.go:523: done waiting for running hooks

Oct 21 23:21:32 penguin snapd[1912]: overlord.go:504: Released state lock file

Oct 21 23:21:32 penguin snapd[1912]: daemon stop requested to wait for socket activation

Oct 21 23:21:32 penguin systemd[1]: snapd.service: Deactivated successfully

Any insight into this matter would be much appreciated ^~^ I’ve attempted this a couple-o-times, but honestly should have put more effort into making sense of this. Thanx again!

Sincerely,

Jess

Bumping this up, bc an answer I do desire. Thank you.

Debian has some issues with apparmor, because Apparmor still needs some downstream patches to work perfectly for snaps.

CC: @zyga

Hi are you perhaps running this in a container? Snapd needs to be able to mount squashfs images but it seems this is denied in your case. Can you tell us more about you system please?

This does not seem to be related to apparmor.

1 Like