Hi to all,
I am trying to install snapd inside lxc of ubuntu 22.04. This was previously ubuntu 21.10 and everything worked fine, but after the upgrade it does not work.
I get this error:
root@ubuntu-gui:~# apt install snapd
Reading package lists... Done
Building dependency tree... Done...
Hi guys, I have googled this extensively and have been unable to get snap packages working in a ubuntu container.
I've enabled fuse & nesting in my container. I've tried to follow the following post...
Snapd installs in an lxc with fuse and squashfuses and fuse installed first (and a few conf file adds), but when you go to run a snap, you get:
"cannot open freezer cgroup (/sys/fs/cgroup/freezer): No such file or directory"
I suspect it has something to do with the v2 cgroups thing, but no...
I got the following error messages while doing snapshots on my Debian 10 running container
failed to open /snap/core/11187: Permission denied
failed to open /snap/core/11167: Permission denied
failed to open /snap/certbot/1201: Permission denied
failed to open /snap/certbot/1150: Permission...
We are running the wekan snap package in an LXC container and it works well, but about once a day, it completely freezes, stops responding to ping requests.
Only way to stop it is lxc-stop -n 121 --kill and restart it using pct start 121.
The container's /var/log/syslog just stops at the time...
Ich habe ein Problem mit snapd in Ubuntu 18.04 lxc Containern. In meiner lxc config habe ich bereits folgendes hInzugefügt.
I can start the snapd container with rocketchat server but in syslog I have the following error...
I have a ubuntu lxc - container with ubuntu 18.04 and installed snapd, but with problems. In my lxc config I have the following lines added:
I can start the snapd container with rocketchat server but in syslog I have the...
I've been trying to get snapd to work in lcx containers butIi get errors on both debian 9 and ubuntu 18.04.
I'm using a single node Proxmox VE 5.4-8 that is updated as of 05-july-2019 on the no-subscription repositories with the exception being that pve-manager is still 5.4-8 and not 5.4-10.