New server has been acquired. Debian 13 has been installed.

GS308EP switches have been acquired and installed.

Now, I’m working to migrate to the new machine. 3 1/2 years ago when I started futzing with Docker, I sorta followed guides and guessed, abused it trying to make it do things it wasn’t designed for, and flipped switches I likely shouldn’t have flipped, so the set up is more than a little shabby.

As a result, I’ll likely end more redeploying than migrating the containers.

So rather than go forward with Docker blindly, I want to reassess whether I shouldn’t look into Proxmox, LXC, or Podman instead of Docker, or maybe something else entirely?

Work is just about done dumping ESX for Nutanix, but both of those seem overkill for my needs.

Of course the forums for any of the solutions make their own out to be the best thing since sliced bread and the others useless, so I’m hoping to get a more nuanced answer here.

  • Vendetta9076@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    1
    ·
    16 hours ago

    I use proxmox has the base OS to deploy different virtual machines/LXCs depending on what I need. I have a dedicated docker lxc among those. Say what you will about docker, and man do people have opinions, but proxmox is probably the best way to run a multi lxc/VM setup. Highly recommend regardless of what else you do.

    • Imacat@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 hours ago

      Same here and it’s worked well. I migrated my arr stack from another machine where it was in docker and just couldn’t see a reason to spend a bunch of time rebuilding it with LXCs.

      • felbane@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 hours ago

        It’s not worth the headache IMO. Just run a docker VM and use lxc for the one-off systems that you want to experiment with.

        I have a “production” docker VM and a “sandbox” docker VM and prod only ever runs compose files that I’ve vetted in sandbox. Super stable, basically bulletproof, and still has the flexibility to experiment and break stuff without affecting my core services.

      • Scrubbles@poptalk.scrubbles.tech
        link
        fedilink
        English
        arrow-up
        1
        ·
        12 hours ago

        Only pain will you find down that path. I did that for years, but it’s a pain. You have to disable so many security features, and I found it to be incredibly brittle. I found myself fearing all proxmox upgrades because each time it would break the lxcs. I wish you luck

      • uncloaked@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        16 hours ago

        I used proxmox helper scripts for portainer lxc and would get my host system kernel panicked from backing up the lxc that had a NFS share mounted with fstab. Solved it with moving to komodo lxc and setting the NFS share being mounted directly to the container with Docker Compose.if you decide portainer you can set that up with stacks feature. Hope that helps.

    • SpikesOtherDog@ani.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      16 hours ago

      I am using proxmox to host my docker machine as well. I’m also using it to host a W11 machine for just-in-casies. Third machine so far is a VM for testing.