snapd package not working

Walk3r

Member
Jan 16, 2020
13
0
21
35
Hy I don't really know whats going on here.
I managed to install snapd in my debian 11 lxc container.
I can install snapd packages but they don't work.
When i install tautulli service,
it's status look like this:

Code:
systemctl status -l snap.tautulli.tautulli.service
* snap.tautulli.tautulli.service - Service for snap application tautulli.tautulli
     Loaded: loaded (/etc/systemd/system/snap.tautulli.tautulli.service; enabled; vendor preset: enabl>
     Active: failed (Result: exit-code) since Wed 2022-06-29 23:38:55 CEST; 13s ago
    Process: 1115 ExecStart=/usr/bin/snap run tautulli (code=exited, status=1/FAILURE)
   Main PID: 1115 (code=exited, status=1/FAILURE)
        CPU: 23ms

Jun 29 23:38:55 NAS systemd[1]: Started Service for snap application tautulli.tautulli.
Jun 29 23:38:55 NAS tautulli.tautulli[1115]: aa_is_enabled() failed unexpectedly (No such file or dire>
Jun 29 23:38:55 NAS systemd[1]: snap.tautulli.tautulli.service: Main process exited, code=exited, stat>
Jun 29 23:38:55 NAS systemd[1]: snap.tautulli.tautulli.service: Failed with result 'exit-code'.
lines 1-11/11 (END)...skipping...
* snap.tautulli.tautulli.service - Service for snap application tautulli.tautulli
     Loaded: loaded (/etc/systemd/system/snap.tautulli.tautulli.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2022-06-29 23:38:55 CEST; 13s ago
    Process: 1115 ExecStart=/usr/bin/snap run tautulli (code=exited, status=1/FAILURE)
   Main PID: 1115 (code=exited, status=1/FAILURE)
        CPU: 23ms

Jun 29 23:38:55 NAS systemd[1]: Started Service for snap application tautulli.tautulli.
Jun 29 23:38:55 NAS tautulli.tautulli[1115]: aa_is_enabled() failed unexpectedly (No such file or directory): No such file or directory
Jun 29 23:38:55 NAS systemd[1]: snap.tautulli.tautulli.service: Main process exited, code=exited, status=1/FAILURE
Jun 29 23:38:55 NAS systemd[1]: snap.tautulli.tautulli.service: Failed with result 'exit-code'.

my lxc.conf:
Code:
arch: amd64
cores: 4
features: fuse=1,keyctl=1,nesting=1
hostname: NAS
memory: 10240
mp0: Storage:subvol-100-disk-0,mp=/mnt/Storage,backup=1,size=17000G
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.178.1,hwaddr=E2:41:43:01:3E:7F,ip=192.168.178.100/24,type=veth
ostype: debian
parent: snap2
rootfs: local-lvm:vm-100-disk-0,size=180G
swap: 4160
unprivileged: 1
lxc.cgroup2.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dir

udev status returns this:
Code:
systemctl status udev
* systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: inactive (dead)
TriggeredBy: * systemd-udevd-control.socket
             * systemd-udevd-kernel.socket
  Condition: start condition failed at Wed 2022-06-29 23:38:11 CEST; 7min ago
       Docs: man:systemd-udevd.service(8)
             man:udev(7)

what ive done:
Code:
sudo apt install squashfuse fuse
sudo apt install snapd
sudo snap install core; sudo snap refresh core

sudo snap tautulli
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!