At this point, I’ve got a lot of containers already running on my system, all in separate directories in my home directory. They’re each set up with a docker-compose file, and all of the volumes are just directories within those directories.

I don’t really want to change this setup, because it allows me to easily rip it all out and transplant it to a new system.

What I’d like is a web UI to see all of these containers, view their status, and potentially reboot them. It would also be great to be able to spin up VMs (not containers, but actual VMs) with it.

I’ve heard of Portainer, but haven’t had any experience with it.

What are your suggestions, and why do you recommend them?

@hperrin@lemmy.world
creator
link
fedilink
English
28M

Thanks. I did check it out and it looks like it’s got some really cool benefits, like being able to cluster across two machines and take one down if it needs servicing, with zero down time.

I’m thinking about buying some rack mount servers and bringing everything I’m currently doing in the cloud for my business to on-premises servers. The one thing I was wary about was how I was going to handle hardware maintenance, and this looks like it would solve that issue nicely.

@Gooey0210@sh.itjust.works
link
fedilink
English
3
edit-2
8M

For the system itself I would recommend nixos

Some people like it, some people are against progress and they think work should be manual 🤣

I’m using nixos and all my machines, even integrating my phone in it

You can automate and replicate unbelievable stuff with it. You solve a bunch of problems by using nixos

But it’s a whole big rabbit whole, and it would take a lot of time to learn how to use it, then a lot of time to set everything up

But you could do zero downtime hardware maintenance without VMs or containers, just by using bare metal

Edit: or with VMs, containers, or k8s. Everything would be just cleaner and cooler

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 279 users / day
  • 589 users / week
  • 1.34K users / month
  • 4.55K users / 6 months
  • 1 subscriber
  • 3.5K Posts
  • 70K Comments
  • Modlog