On 2021-06-11, Neal Gompa <ngompa13@gmail.com> wrote:
On Fri, Jun 11, 2021 at 7:15 AM Jan Engelhardt <jengelh@inai.de> wrote:
On Friday 2021-06-11 12:55, Martin Wilck wrote:
On Fr, 2021-06-11 at 18:03 +1000, Aleksa Sarai wrote:
I just ran into this bug today, and I realised that this bug actually also affects users who run containers on *different hosts* that have ZFS as the backing filesystem. For instance, running Tumbleweed on Ubuntu (which has ZFS as the default filesystem) will result in this error being triggered. (I personally run LXD containers on openSUSE with a ZFS storage driver, but this same thing would happen with Docker or LXD on Ubuntu or any other distribution with ZFS.)
You run "zypper dup" in the container? Can't you just update your container image?
Not everything runs on orchestration where you can rebuild from scratch. Think systemd-nspawn. There just is no image facility as far as that's concerned. It's just you and a directory tree.
LXD is image based, just like OCI container systems are.
LXD does have images but they're not like OCI/Docker images and there isn't a "docker build"-like ecosystem. LXD images are basically just a tar-ified version of a distribution's root filesystem and there are no layers. LXD containers are managed more like VMs -- you can use other tools on top to get a more infrastructure-as-code-style model (such as OpenShift) but at its code LXD containers don't really have anything akin to Dockerfiles. -- Aleksa Sarai Senior Software Engineer (Containers) SUSE Linux GmbH <https://www.cyphar.com/>