Portainer VS podman-compose

Portainer - Makes managing my homelab, gateway and (Pi0) DNS server extremely easy and fun. Traefik - Great companion for the above. For those who don't know for some reason - a simple, yet extremely powerful reverse proxy. Docker - Should be obvious, but I would feel bad if I didn't give it a shoutout. If you haven't heard of it - go and learn, please, it'll make your life beautiful.

Portainer - Web UI for managing Docker Containers

> Why there are needs to use docker GUIs?

Because to some people using GUIs are more approachable and in some case objectively better (e.g. telling the state of things at a glance and efficiently using screen real estate, with graphs and whatnot), whereas the ways they're worse in might not dealbreakers (e.g. lack of automation, given that there can still be APIs or access to the underlying cluster anyways).

For an example of this, see pieces of software that one can use to manage orchestrators:

- Portainer: https://www.portainer.io/

- Rancher: https://www.rancher.com/products/rancher

Some orchestrators even include dashboards on their own:

- Kubernetes dashboard: https://kubernetes.io/docs/tasks/access-application-cluster/...

- Nomad web UI: https://developer.hashicorp.com/nomad/tutorials/web-ui

And some of that applies to running regular containers and managing them locally: for many it can be useful to be able to just click around to discover more details about a container, as well as what's using storage and so on. Thankfully the CLIs of Docker and competing runtimes are pretty well structured as they are, but I guess it's just a different type of UX.

At the end of the day, what works for you, or even what you find comfortable to use, might not be the case for someone else and vice versa. It's definitely nice to have that choice in the first place, and to know the various options out there.

- Portainer

Breaking it down a bit more: - 'handle_path /docker/' means to handle on calls to http://example.tailnet-def456.ts.net/docker/ - 'reverse_proxy / portainer:9000' means to reverse proxy those calls to "portainer" (that's the container name on the docker network) on port 9000. That's where I have hosted my docker manager (https://www.portainer.io/)

From purely an administration standpoint, I'd recommend Cockpit. For Docker, I'd also recommend Portainer. Maybe for Minecraft, try out Pterodactyl - I personally haven't used it myself but I've heard good things about it.

Portainer - Web UI for managing Docker Containers

Not sure if it related to your problem, but seeing you using dns and podman-compose state:

theres podman-compose :)

Note that this single image spawns multiple managers using profiles from the MANAGERS_CONFIGS environment variable. If you use podman instead of docker, install podman-compose as well.

Easiest is probably https://docs.budibase.com/docs/docker-compose . You have a choice, use Docker or use Podman. Podman may not work with their docker compose config out of the box, would probably have to add an selinux label to the volume mount paths (ie: - host/data:container/data:z )

There is an alternative software that is mostly compatible with docker-compose: podman-compose supports providing extra arguments, so you would need to use podman-compose instead.

Podman itself does not support Docker Compose to launch multiple containers locally. There are two alternatives for this. First, there is already a project called Podman-Compose that is supposed to fulfill the core functionalities of Docker-Compose, and second, Podman supports the pods described above. These can also be used to launch and manage multiple containers at once - even via a more Kubernetes-friendly path.