Just got an email thanking me for being a 5-node/free user, but Portainer isn’t free and I need to stop being a cheap-ass and pay them because blah blah economic times enshittification blah blah blah.
I’ve moved off them a while ago, but figured I’d see if they emailed EVERYONE about this?
A good time to ditch them if you haven’t, I suppose.
portainer sucks anyways. shells dont work really. dockGE is free. https://github.com/louislam/dockge
I used portainer only as fancy docker dashboard and to start stop services. It was buggy and even with the git implementation really frustrating to use. Also that they do not store the compose files is simply not ok.
Dockge fully replaced portainer for my needs.
Portainer does store compose files though? I’ve manually used docker compose commands from the folders Portainer saves them in. They’re labeled with numbers instead of project names which makes it difficult to know which one you’re looking for, but I use rga so that wasn’t as much of an issue for me as it would have been otherwise. It was tedious, but the compose files very much exist on your hard drive.
I love Dockge. Have also replaced Portainer with it.
But I hate that I can’t just restart a single container easily with it. It’s a small enough issue since most of the time I need to restart the entire compose file because of dependencies, but still.
To be fair, Dockge is very, very new. I imagine features like that will turn up soon enough.
Oh most def.
I guess I’m complaining that it isn’t already there, but honestly I love Dockge. Won’t be going back to Portainer. Pretty much since the beginning I’ve been using compose files, and it always bugged me how Portainer handled them.
Dockge is what I’ve always wanted, tbh. Just some QoL stuff here and there, but I’m very happy with it :)
You can go to the terminal tab and just run the cli command.
Not perfect, but something to avoid needing to ssh in at least.
Just for you to known, they store the compose file. It’s in their compose folder on the data volume.
Oh yeah, sorry i know. Was too lazy to type it out. They number the created compose files in numbered directories instead of naming it after the stack.
The problem is, that they do not support at all the direct modification of those files and the abstraction of numbering them instead of giving them real names is annoying when you want to start them via cli.
I dont ever recall giving portainer my real email.
Why would you bother? Portainer isn’t anything very useful for Docker. Set up your compose files and go to bed.
Lazydocker if you need an SSH TUI.
I’ve never really seen why portainer is used beyond a shiny UI. Docker compose file is enough for me
Terminals are powerful and flexible, but still slower than a dedicated UI to see states at a glance, issue routine commands, or do text editing.
Terminal absolutists are as insufferable as GUI purists. There is a place and time for both.
Beautifully said. I can’t say I’ve come across too many GUI purists, but I’ve definitely been shamed by terminal absolutists who are fine with turning a 1 second process into a 10 second one. There’s a time and place for both.
See also: bass players who use a pick.
Wtf at y’all talking about, it’s usually way faster to do these things in terminal. I guarantee I can restart a docker container faster with a terminal then you can with a browser.
Alt+enter brings up a terminal, then I type literally “ssh server” and I’m ssh’d into the box. ‘sudo docker restart containername’ and the password and I’m done before Firefox even loads for your dumbass and I didn’t even have to lift my hands from the keyboard. And for common and repeatable tasks there are these things called aliases and the ability to chain commands. I can condense all of that to a single command. Lmao. GUI plebs are so annoying with their ignorance
That’s what aliases / functions in .bashrc (or whatever shell you use) are for. You don’t need to always write the full code.
EDIT: Looks like .bashrc hurt you guys.
Being a terminal purist is wonderful for those of us who live our lives deep in the caverns of Linux, but in actual production use you very often find situations where less technical users have to interact with the systems that we build.
For my work, I need a way for low level tech support and technicians to go in and restart a container from time to time, and these people curl up in a ball and scream if you show them a command prompt. Having a UI removes a lot of friction.
