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.
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.
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.
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.
UI, just too many annoyances. Fkr example the cut off unhelpfull error messages
compose files, like this project calls it are taken hostage by portainer
git, while you can use a repository there is no comfortable way to test out changes and commit them to git. Would portainer use a sinple file structure for compose files that would not be a problem
Ads, they try to promote there business version via the UI.
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
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Wow! This is beautiful!
I’ll definitely be checking this out, thanks for the link
This is also by the author of Uptime Kuma, which explains the similarity in UI.
I saw the logo and thought it looked TOO familiar
FUCK. YES.
This sounds like exactly what I have been looking for.
Is it a replacement for Unraid docker compose plugin?
Finally! Goodbye Portainer!
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.
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).
I use an ad-blocker to strip those out
“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.
https://github.com/ngxson/portainer-ce-without-annoying
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.
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
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