I run a small server with Proxmox, and I’m wondering what are your opinions on running Docker in separate LXC containers vs. running a specific VM for all Docker containers?

I started with LXC containers because I was more familiar with installing services the classic Linux way. I later added a VM specifically for running Docker containers. I’m thinking if I should continue this strategy and just add some more resources to the docker VM.

On one hand, backups seem to be easier with individual LXCs (I’ve had situations where I tried to update a Docker container but the new container broke the existing configuration and found it easiest just to restore the entire VM from backup). On the otherhand, it seems like more overhead to install Docker in each individual LXC.

  • MangoPenguin@lemmy.blahaj.zoneEnglish
    10·
    2 days ago

    Regardless of VM or LXC, I would only install docker once. There’s generally no need to create multiple docker VMs/LXCs on the same host. Unless you have a specific reason; like isolating outside traffic by creating a docker setup for only public services.

    Backups are the same with VM or LXC on Proxmox.

    The main advantages of LXC that I can think of:

    • Slightly less resource overhead, but not much (debian minimal or alpine VM is pretty lightweight already).
    • Ability to pass-through directories from the host.
    • Ability to pass-through hardware acceleration from a GPU, without passing through the entire GPU.
    • Ability to change CPU cores or RAM while it’s running.
    • non_burglar@lemmy.worldEnglish
      1·
      2 days ago

      I use individual lxc for each docker compose so I don’t have to revert 8 services at once if I need to restore.

      I would also argue that an alpine lxc runs in 22mb ram by itself … Significantly smaller footprint on disk and in memory. But most importantly, lxc can actually share memory space effectively, one doesn’t need to reserve blocks of ram.

      • sugar_in_your_tea@sh.itjust.worksEnglish
        5·
        2 days ago

        You don’t have to revert 8 services, you can stop/start them independently: docker compose stop <service name>.

        This is actually how I update my services, I just stop the ones I want to update, pull, and restart them. I do them one or two at a time, mostly to mitigate issues. The same is true for pulling down new versions, my process is:

        1. edit the docker-compose file to update the image version(s) (e.g. from 1.0 -> 1.1, or 1.1 -> 2.0); I check changelog/release notes to check for any manual upgrade notices
        2. pull new images (doesn’t impact running services)
        3. docker compose up -d brings up any stopped services using new image(s)
        4. test
        5. go back to 1 until all services are done

        I do this whenever I remember, and it works pretty well.

      • MangoPenguin@lemmy.blahaj.zoneEnglish
        2·
        2 days ago

        How do you handle backups? Install restic or whatever in every container and set it up? What about updates for the OS and docker images, watchtower on them I imagine?

        It sounds like a ton of admin overhead for no real benefit to me.

        • non_burglar@lemmy.worldEnglish
          1·
          1 day ago

          I just snapshot the parent lxc. The data itself isn’t part of the container at any level, so if I bung up compose yml or env, I can just flip it back. The only real benefit is that all my backups are in the same place in the same format.

          Like I’m not actually opposed to managing docker in one unit, I just haven’t got there yet and this has worked so far.

          If I were to move to a single platform for several docker, what would you suggest? For admin and backups?