Comment on Today at 50+ I feel like a little kid ... what a homelab ...

• jjlinux@lemmy.zip ⁨1⁩ ⁨month⁩ ago

  So, in my case at least, having services spread across LXC containers and VMs, instead of various dockers stacks directly under on host, allows me to provide each service with its own internal IP address as opposed to having to worry about setting up 2 services with the same port because I can’t remember I was already using that port. It’s just cleaner that way.

  Additionally, I get to create containers with the specific needs for each service to run comfortably.

  It also allows for easier deployment and testing without much danger of ruining the host in something like CasaOS for example. If I have to make some adjustments to the host machine to make a docker stack run better, have more accesses, etc., I can have at it without fear that those changes could affect other docker stacks in the same host, because all hosts are contained.

  Then there’s the ease of management and deploying fully functional services with one line in the CLI of the host.

  After running UnRaid, OMV, CasaOS and a few others, Proxmox has been the one system that is just so intuitive that I don’t really have to think about it much. For the most part, deployments of pretty much anything just work.

  original

  • q7mJI7tk1@lemmy.world ⁨1⁩ ⁨month⁩ ago

    You can run docker stacks with external IPs, no? I run all mine from Unraid, through Dockhand as compose stacks, with some ports on the host, others as external IPs on VLANs. But yes, like you I would actually like to move them to VMs so it’s easier to backup, and service, without taking the host server offline.

    It starts to get like Inception levels of depth on VMs and hosts!

    original
  • wibble@reddthat.com ⁨1⁩ ⁨month⁩ ago

    Time to revisit my old habits

    original