3 ms·
Moved back to Debian because of lxc on Ubuntu requiring snaps. Turns out same problem on Debian. Snapd consumes 100% cpu. All. The. Time. Hoping Bookworm will s
by 28304283409234 3y ago
Moved back to Debian because of lxc on Ubuntu requiring snaps. Turns out same problem on Debian. Snapd consumes 100% cpu. All. The. Time. Hoping Bookworm will solve it. Else I will be moving to Archlinux, which has lxc without snapd.
- yokem55 3y agoBookworm now has lxd as natively packaged deb's in the main repository. It's very nice to setup.
- yrro 3y agoI don't think lxc on Debian has ever needed snapd? https://packages.debian.org/bullseye/lxc https://packages.debian.org/bullseye/lxc
- aragilar 3y agoThey're probably running lxd (which is only packaged for snap as far as I know), lxd is controlled by the "lxc" command (which isn't part of lxc...).
- yrro 3y agoAh. This questionable decision is why I abandoned LXC for Docker (initially) and eventually Podman/k8s.
- sm1ch 3y agolxd (not just lxc) is now also available as a deb package in debian: https://wiki.debian.org/LXD https://wiki.debian.org/LXD https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768073 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768073
- aragilar 3y agoThe "lxc" command runs lxd, you need to run "lxc-'command'" for actual lxc.
- CoolCold 3y agoInteresting - I don't observe such behavior with snap/lxd on my Ubuntu 20.04 and 22.04 boxes. Not a heavy user though - maximum 15-20 VEs (virtual enforcements) per server.