27
submitted 10 months ago by hperrin@lemmy.world to c/selfhosted@lemmy.world

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?

you are viewing a single comment's thread
view the rest of the comments
[-] MigratingtoLemmy@lemmy.world 6 points 10 months ago

If you're running a compatible OS (Debian will work), cockpit for VMs and whatever you like for containers.

Or just do everything on the command line like us crusty system admins

[-] CapillaryUpgrade 1 points 10 months ago

Cockpit is great.

It's pretty simplistic. It gives you an overview of your system ressources and handles libvirt VMs and Docker (i think. I used it with Podman, but in this context both should work).

My impression was that the container and VM interfaces were pretty simple, and I wouldn't have liked it as my main interface for those services, but it would be perfect for getting an overview and restarting them!

this post was submitted on 28 Jan 2024
27 points (96.6% liked)

Selfhosted

40555 readers
286 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.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS