7
submitted 2 weeks ago* (last edited 2 weeks ago) by valar@lemmy.ca to c/selfhosted@lemmy.world

What to people use and recommend for this? I've read a bit about portainer, but I'm still learning - and don't know what the best solutions are.

Today I have a handful of selfhosted services running on my home machine - mostly installed directly, but a couple running as docker containers. As the scale of my selfhosting has grown, I've realized that things would be a lot easier to manage if each service was run as its own container, so that installed services are isolated.

The solution I'm looking for would make it easy (possibly a web UI) for me to monitor, modify, update, and remove containerized services, including networking and storage.

Edit: Also I would only want a FOSS solution.

top 15 comments
sorted by: hot top controversial new old
[-] danielquinn@lemmy.ca 1 points 2 weeks ago

Kubernetes. For a homelab, the stripped-down k3s is fantastic and surprisingly easy to get going.

Once you've got Kubernetes set up, you can lean on all the many tools already out there for things like deploying complex projects (Helm) and monitoring (Prometheus/Grafana). OpenLens is a nice piece of software you can use to monitor and control your cluster too, as is k9s.

[-] irotsoma@piefed.blahaj.zone 1 points 2 weeks ago

What do you use for repeatable recovery and deployment of systems?

I've looked at ArgoCD and FlexCD. ArgoCD was too flaky. When I made changes to helm files it would often fail to deploy them and the UI often wouldn't really show the detailed errors from things like helm syntax errors, so it was a pain to troubleshoot.

FlexCD was just really a pain to configure in the first-place and I didn't want to learn kustomize when I already have helm charts.

And neither really supported staged deployments or dealt with dependant services well. So I couldn't get it to deploy the infrastructure level helm charts like PostgreSQL before deploying the services that depend on it. Technically, with Kubernetes it shouldn't matter about the order of deployment but in reality when ArgoCD would deploy the other stuff first and wait for it to come up and it never came up because the dependencies weren't there, it caused it to choke a lot.

Just an example of the issues I've had. But I really want an easy way to make lots of small changes to charts and deploy them quickly as well as being able to quickly recover the cluster from backups if something catastrophic happens like a fire without having to manually deploy each chart. Just curious how others handle it or if it's always manual deployment of charts via CLI only.

[-] jrgd@lemmy.zip 1 points 2 weeks ago

Might take a little bit of effort to do a conversion if you're locked into explicitly how Docker interacts with OCI containers, but over in the Podman camp you have two options.

  • Cockpit with the Podman containers interface: a graphical web-based solution for managing podman containers and the rest of the system.
  • Podman Quadlets: a config file-based way to manage Podman containers, volumes, pods, networks with custom SystemD units. Great if you want to version control your deployments.

Other than that, the more usable solutions I've tried of graphical Docker container management interfaces would be the ones in Unraid and Proxmox, though those solutions may not be suitable depending on your use case and have their own caveats to be aware of.

[-] Novi@sh.itjust.works 1 points 2 weeks ago

Dockge - https://github.com/louislam/dockge

Docker compose with webui and upgrade button.

[-] Joker_1902@lemmy.ml 1 points 2 weeks ago

I personally like dockge, it’s simple and lightweight and I like the fact that the webui has a good phone interface.

[-] RanchBranch@anarchist.nexus 1 points 2 weeks ago

I personally have switched over to Komodo after using portainer for years. Never looking back, I love it. Works perfectly and can do GUI, compose files, and repos for docker. I also have multiple machines running stuff and it let's me fiddle with everything in one UI.

[-] vegetaaaaaaa@lemmy.world 1 points 2 weeks ago

Podman pods (or quadlets) managed by ansible.

[-] fozid@feddit.uk 1 points 2 weeks ago

I recently moved from docker compose to podman quadlets. Took a bit of effort, but fully foss, and for me it's set and forget. Have about 30 containers across about 12 services. Have them set to auto update and it all runs through systemd.

[-] motruck@lemmy.zip 1 points 2 weeks ago

This is the direction I'm headed. Goodbye docker. Quadlets everywhere. Im in the process of converting docker run scripts currently. Any tips or gotchas you can share that you learned?

[-] GunnarGrop@lemmy.ml 1 points 2 weeks ago

I'd absolutely recommend Kubernetes (k3s/rke2) or podman quadlets. Quadlets are a lot easier to get started with, but are still very flexible.

I'd recommend against using portainer. I tried it quite recently and I did not like it at all. A lot of features are paywalled, and was overall just a frustrating experience. I've heard it was a lot better some years ago.

[-] statelesz@slrpnk.net 0 points 2 weeks ago

Dockhand is great. I haven't touched Portainer ever since.
https://github.com/Finsys/dockhand

[-] valar@lemmy.ca 0 points 2 weeks ago

Thanks, what have you liked about switching to this from portainer?

[-] Kupi@sh.itjust.works 0 points 2 weeks ago

I just recently switched from portainer to dockhand and I really like it. The UI is great and the setup and config wasn’t too complicated. I like that I can put both of my servers into one instance and can update all of my containers from dockhand vs manually. The other thing I like is being able to view the logs for my containers. Idk if it’s a me thing, but whenever I would try to view logs in portainer I would never be able to scroll up as it would update and send me back to the bottom. Again, I could’ve just been doing something wrong, but it always bothered me and I don’t have that issue with dockhand.

[-] Fnaargh@lemmy.zip -1 points 1 week ago* (last edited 1 week ago)

Uncheck auto update/refresh in top right corner

[-] Kupi@sh.itjust.works 2 points 1 week ago
this post was submitted on 12 May 2026
7 points (88.9% liked)

Selfhosted

59509 readers
123 users here now

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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS