Evalulate alternatives to Portainer?

[b-]

Hi!

I'm not a huge fan of Portainer these days, because it's kind of buggy, as well as artificially limited on the free version (especially in regards to its gitops functionality -- and I mean its gitops functionality in particular is both particularly buggy and particularly limited/nonfree...)

Despite these issues, I recognize the importance and usefulness of a GUI to manage containers (especially for a home server), so I wanted to ask if anyone else feels similarly, and to start a discussion about potential alternatives to Portainer.

I've recently come across Komodo (project page) and I really like it and recognize a lot of promise. It definitely is mature enough that I've been replacing all of my own Portainer installations (homelab and a couple of small production managed services I monitor) with it, but it's still, like, a decade younger.

Cockpit has a stalled issue about having built-in podman-compose/Docker Compose support.

There are countless other smaller projects that do the same sort of thing, too, but Komodo is the one I've personally been messing with.

Thoughts?

[castrojo]

Let's do it! Mind PRing it in? We can remove portainer after.

[b-]

Sure, i can try to do something tonight or tomorrow!

I put together some hacky ignition config to spin up a Komodo server and node on ucore, and it uses a systemd service unit I wrote to bootstrap Komodo via docker-compose, because Komodo itself can then manage its own deployment (it can't manage quadlets).

So I'll probably port that over from the ignition file to a script to run while building this.

[gbraad]

While not ideal, I would still rather do a:

$ podman container runlabel INSTALL quay.io/cockpit/ws
$ systemctl enable --now cockpit.service

after deployment. Might actually create the quadlet for this.
Portainer does not understand rootless use of Podman, which is my main use of it.