Comment on Network loss after 24hrs on Docker LXC

emptiestplace@lemmy.ml ⁨6⁩ ⁨months⁩ ago

• skittlebrau@lemmy.world ⁨6⁩ ⁨months⁩ ago

  Not OP, but I run Docker in LXC because my Proxmox host is an Intel NUC and I only have one graphics card (integrated).

  I don’t want to passthrough the iGPU to a VM because then I lose video output for the host. I also don’t want to use SR-IOV for iGPU because it’s buggy and results in garbled output for HDR content. That’s why, in my case, Docker in LXC makes sense.

  source

  • OminousOrange@lemmy.ca ⁨6⁩ ⁨months⁩ ago

    This is mostly my reasoning too. I’ve got a bit more juice than a NUC, but I prefer the way resources are managed with an LXC for the certain apps that I run. I still have VMs for other things, like HAOS and a BlueIris NVR. It’s only a local homelab with no external users so avoiding additional complexity is often in my best interest.

    source
  • emptiestplace@lemmy.ml ⁨6⁩ ⁨months⁩ ago

    Why not just use LXC though?

    source

    • skittlebrau@lemmy.world ⁨6⁩ ⁨months⁩ ago

      Ideally I would, but I don’t have the time to manage 30 different containers.

      When I didn’t have kids, I ran everything in separate LXCs. I decided to just move everything to Docker and move on with my life.

      source
• thirdBreakfast@lemmy.world ⁨6⁩ ⁨months⁩ ago

  My ‘good reason’ is just that it’s super convenient - for backups and painlessly moving apps around between nodes with all their data.

  I would run plain LXCs if people nicely packaged up their web apps as LXC templates and made them available on LXCHub for me to run with lxc compose up, but they generally don’t.

  I guess another alternate future would be if Proxmox added docker container supervision to their web interface, but you’re still not going to have the self-contained neat snapshot system that includes the data.

  In theory you should be able to convert an OCI container layer by layer into an LXC, so I bet there’s projects out there that attempt this.

  Image

  source

  • markstos@lemmy.world ⁨6⁩ ⁨months⁩ ago

    It’s convenient when it works, but with three different containerization technologies, it’s harder to debug when Proxmox+LXC+Docker fails. Even running Docker in parallel to LXC rather than nested would be simpler.

    source
• pyrosis@lemmy.world ⁨6⁩ ⁨months⁩ ago

  Usually this comes down to resource and energy efficiency. While a vm works perfectly fine you will find you can share video and storage resources in efficient ways with lxc.

  For example you can directly pass a zfs dataset into a lxc with a simple lxc.mount.entry:

  This would allow you to configure options like cluster size, atime, compression algorithm, xattr, etc… without much overhead.

  It’s also nice to know you can share your GPU with multiple lxc without it being locked into a single vm.

  source
• OminousOrange@lemmy.ca ⁨6⁩ ⁨months⁩ ago

  Why would one prefer a VM over an LXC for Docker?

  source

  • emptiestplace@lemmy.ml ⁨6⁩ ⁨months⁩ ago

    • Kernel isolation
    • HA
    • Stability
    • It works

    source

    • markstos@lemmy.world ⁨6⁩ ⁨months⁩ ago

      LXC/LXD can be highly available (HA), stable, work and provide kernel isolation as well (real VMs): ubuntu.com/blog/lxd-virtual-machines-an-overview

      source

      • emptiestplace@lemmy.ml ⁨6⁩ ⁨months⁩ ago

        In Proxmox?

        source
      • skittlebrau@lemmy.world ⁨6⁩ ⁨months⁩ ago

        There are some quirks with docker in LXC. Nothing that can’t be overcome, but docker in a VM is definitely more stable.

        source