> It sounds like we must remove seeded snaps from our LXD images, and not install
> any seeded snaps inside our container. And like only install the lxd stub deb.
> Cause it looks like seeding snaps is not supported inside classic lxd containers.
Let's remember that these aren't just LXD images, they are generic squashfs images from cloud-images.ubuntu.com. This raises the issue that if the generic cloud squashfs is run in any environment where snap seeding can not complete then boot is stuck and the instance is broken without cloud-init completing. This might mean no ssh keys and difficulties debugging. So I'll reiterate that this is not an acceptable solution and note that the issue is broader than even just unprivileged LXD containers. Removing all snaps from the squashfs feels like a significant lost opportunity.
@xnox wrote:
> It sounds like we must remove seeded snaps from our LXD images, and not install
> any seeded snaps inside our container. And like only install the lxd stub deb.
> Cause it looks like seeding snaps is not supported inside classic lxd containers.
Let's remember that these aren't just LXD images, they are generic squashfs images from cloud-images. ubuntu. com. This raises the issue that if the generic cloud squashfs is run in any environment where snap seeding can not complete then boot is stuck and the instance is broken without cloud-init completing. This might mean no ssh keys and difficulties debugging. So I'll reiterate that this is not an acceptable solution and note that the issue is broader than even just unprivileged LXD containers. Removing all snaps from the squashfs feels like a significant lost opportunity.