Portainer is changing to a mostly AI and kubernetes supported app.
Indeed… such an awful sorrow…
Such decisions for “AI” is a pure disgrace and a blatant disrespect to the history, experience, dedication, effort… love… of the contributors, developers, artists… people… of the whole project, and the infinitely marvelous history itself…
I will never consider this project for anything, and won’t recommend it to anyone.
There are more appreciated projects also mentioned in the comments, including:
- Dockhand by @Kirk@startrek.website ;
- Arcane by @Zeoic@lemmy.world ;
- Konodo by @FlexibleToast@lemmy.world ;
- Dockge by @girlnamedzero@piefed.zeromedia.vip ;
…Thank you, dear Developers and Artists, People… for actually considering the art, effort, attitude, human… and being careful for the infinitely magnificent history and future…
Dropped portainer years ago. Managing some compose files isn’t hard, and Dockhand is better for managing updates
Portainer has worked well for me but it has so much that I don’t need or use. It looks like Dockhand has a Home Assistant integration which is nice, so I’ll check that out thanks for the rec.
Man, I didn’t even know dockhand had a HA integration, I know what I’m doing when I get home.
I just want to say I transitioned over to Dockhand and I’m glad I did! Thanks again for the recommendation!
Another good option is Arcane. Its project structure gives you a good place to put bind mounts which you can edit the contents of in app (like configs and such). It’s pretty handy. I am in the process of switching to it from komodo for all of my stacks
I completely forgot portainer was a thing and I’ve used compose files for a few years. If I try anything new a unified dashboard (for managing multiple hosts) would be cool.
Definitely checkout dockhand. It gives a single dashboard for all your hosts. I primarily use it for updating containers and checking logs, but it does quite a bit more. You can even point it towards your compose files and it can edit them in with a GUI, but I haven’t played with that yet.
Guess I’ve figured out how I’m going to spend my Friday evening.
How do you manage updates? I’ve been relying on watchtower
I used to use watchtower. But then it killed a few services that had pre-update instructions, and I learned my lesson.
It just gives me a GUI to see when a service needs an update, and a button to perform it, then I just backup and read the update notes before I do it.
Do you know if there’s a way to pin to a version but have dockhand tell me if there is a new latest version tagged? Not having a clean rollback method is driving me nuts.
Yeah, version tags work fine. All my containers come from compose, and it follows whatever tags I declared there.
That’s my problem I mean. I want to use the tag (e.g. v8) but then be notified when v9 is out. And v8.1. I know the 8.1 would work.
Ahh, I’m not sure about that, you’d have to check the docs.
That sucks. It was one of the few GUIs that did a good job with most aspects of Docker Swarm. I knew it was heading in a shitty direction, but I was hoping something else would come along to fill the gap in the mean time.
I dumped Portainer on my home server when they did the ‘Fortnite’ graphical rebranding. Now using Arcane to manage my servers and edge nodes. Very much enjoying the CVE scan tools and in-place image updating.
I just finished setting up Komodo because I couldn’t find other alternatives that seemed to fit my needs. I didn’t see Arcane amongst those ones I researched. Neat, thanks.
I love Arcane, it’s a great tool
My devs prefer Docker, and don’t want Kubernetes! We have a fix for that: Portainer-D2K. Portainer-D2K is a Docker translator for Kubernetes
As someone who was using mostly podman and is now switching to kubernetes I can confidently say that the cli interface was not what was holding me back. Instead it was the sheer amount of setup and complexity kubernetes can bring into an environment. Kubernetes is great when you want most or all the features it offers, it is horrible if you want to deploy 3 containers for your application on one host.
Oh well, not like I have to care, I wasn’t interested in portainer to begin with.
I use 100% kubernetes at work and help other teams get their app working but at home I don’t run anything that supports it.
Right? Why do they offer a community version and a pro version that’s free for 5 nodes - meaning very small environment, your typical homelab - and push so much for stuff used to manage enterprise-sized deployments?
They want to be a competitor to openshift and rancher.
Welp, no more portainer for me
Embarrassing
Having read this whoke thread, i feel its time to drop Portainer. I find it useful to edit the stackfile and do updates, as well as cleaning old volumes and images. Seems like Arcane and Dockhand are the most popular substitutes. Is the migration from Portainer easy?
I’d also recommend Dockge. Made by the same dude who does Uptime Kuma. Super simple, works along existing stacks.
I started migrating last night. You have to stop your running instances, copy over the yaml and change the volume mounts if you used named volumes.
Portainer was outdated 5 years ago, and it sucked at the job it did.
I’ma stick with dockge and argocd
Dockge hasn’t been updated in a while though. Does not matter for me since my setup only runs in local network but I am not sure how safe it is for online use.
I went from Dockge to Dockhand, though both are good. Dockge was my UI of choice for the last couple of years, so slim and simple. I tried Dockhand on a whim and the extra features won me over, without having a bazillion buttons and confusing UI.
For a lot of my remote hosted services managed with compose, I’ve just been hand rolling the compose files and ssh’ing in.
How do you detect outdated containers?
I was using the watchtower updater until it got archived, thankfully there is a maintained fork now
https://github.com/nicholas-fedor/watchtower
I still need to figure out a auto update solution for my Argo managed services
Not who you responded to, but I do the same and have Pullio set up, which is lightweight and easy enough for my uses cases.
I have a few containers set up for notifying only, but most my services I just let auto-update
dockcheck
This was obvious to anyone who’s used it for any length of time. I’m just surprised the monetisation enshittification didn’t win the race.
The only thing I’ve used Portainer for in the last few years is to easily tidy up my old images.
Sure, it’s trivial on CLI, but why not. 😄 In short: nothing of value lost.
I switched from Portainer to Komodo a while back. I like how everything is declarative. It almost has a Argo CD feel to it without needed kubernetes.
Declarative is awesome.
Maybe it helps if you have a gigantic stack of containers, but I’ve honestly never seen the point of Portainer when I can just look at my compose file.
Does your compose file in itself give you a nice, easily readable status display, analytics, metrics, logging, etc. interface?
Logging, logging into the shell and network creation was my singular use case for portainer.
No, but I’ve never needed them.
I set it up years ago when I still had Ubuntu desktop running on an old laptop. Just kept using it even after using and learning kubernetes at work on an enterprise scale. Also the automatic image checks, easy to check metrics, logs, and endpoints. I have 33 containers right now, it’s just simple to see them all in one screen.
Switching to Podman. Supposedly Cockpit has a gui for it.
Phew. Dodged a bullet just by adhering to SLSA.
Portainer was a great start into docker, but it’s so much easier and better to just use compose and cli. Lazydocker if you really want point and click.
I still have my old install running on my homebrew NAS, but all it’s doing is running plex and a Minecraft server. I need to rebuild, at which point it goes.
Sorry portainer, I appreciate the start, but I’ve got it from here…
I don’t get the only cli mindset, in enterprise and home lab it’s great to have monitoring and insight into what’s running.
It’s personal preference. I grew up staring at green screens. I am at home pawing through config files, I like seeing things from the bottom up.
So, portainer was a nice easy button to ease my transition from VMs to containers, but just like VMWare, I started on the GUI, eventually moved to CLI.
