- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Features:
- Manage
compose.yaml- Create/Edit/Start/Stop/Restart/Delete
- Update Docker Images
- Interactive Editor for
compose.yaml - Interactive Web Terminal
- Reactive
- Everything is just responsive. Progress (Pull/Up/Down) and terminal output are in real-time
- Easy-to-use & fancy UI
- If you love Uptime Kuma’s UI/UX, you will love this one too
- Convert
docker run ...commands intocompose.yaml - File based structure
- Dockge won’t kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal
docker composecommands
- Dockge won’t kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal
Finally! Goodbye Portainer!
Not sure this would entirely replace portainer for me since that manages multiple machines, but I am keen to play with this
This was my first thought as well. This isn’t a replacement for portainer agents on mulitple docker hosts, hopefully that’s something that is doable in the future.
Sounds easy enough to implement tbh, will maybe take a look later how much work that’d be because it’s a must have for me as well
I ditched portainer earlier this year to use the command line only, and don’t miss it at all. If you’re only using docker compose, I really don’t see the point of it.
The CLI is just fine. But a Dashboard can give you a much better and faster overview of everything. (Color highlighting and so on)
What’s wrong with Portainer?
A lot of smaller things, at least for me. The biggest grievance I have with it is the garbage tier UX between hitting “Deploy” on a stack and getting ito to do so. Error messages in the notification bubble get cut off, are unhelpful amd/or disappear too fast. That and the L9g Voewer sucking ass are my main problems with it and why I’ll definitely check this out.
Not to mention that there’s no way to view those errors messages after the pop disappears (which happens automatically after a few seconds), so God forbid you hit the washroom or check Lemmy while your stack is deploying, no you have to watch that fucker like a hawk.
It is fucking ridiculous that I have to copy and paste error messages just to see what they say.
Portainer has so many tiny broken places that I effectively treat it only as a read-only view. It lists my containers and shows my logs and nothing much else.
It could in theory do quite a bit more, but starting from the fact that it doesn’t quite do docker-compose, but its own thing that’s somehow similar but different there’s just too many tiny issues with it.
Also, it’s quite aggressively pushing the paid option without a way to turn that off (or at least turn it down to tolerable levels).
“Read only view” is exactly how we’ve started treating it. We used to deploy entirely through Portainer, now we work from the command line and just use Portainer as an information layer. And it frankly sucks at that. Doesn’t even give you preformance metrics.
I use an ad-blocker to strip those out
https://github.com/ngxson/portainer-ce-without-annoying
I could close my eyes to all of those, but the issue that pisses me off the most is that often enough Portainer just forgets which stacks it has ownership over, forcing you to delete the whole stack, dig up the old compose from its files, and create it again