Comment on Docker in LXC vs VM

• sugar_in_your_tea@sh.itjust.works ⁨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)
  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.

  source

  • non_burglar@lemmy.world ⁨1⁩ ⁨day⁩ ago

    Oh, nice. Thanks!

    This is me showing my docker ignorance, I suppose.

    source
• MangoPenguin@lemmy.blahaj.zone ⁨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.

  source

  • non_burglar@lemmy.world ⁨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?

    source