posted in Selfhosted
Portainer 3.0 is coming, and here's what it means for you — Portainer
Portainer is changing to a mostly AI and kubernetes supported app.
portainer.io/blog/portainer-3-0-is-comingposted in Selfhosted
Portainer 3.0 is coming, and here's what it means for you — Portainer
Portainer is changing to a mostly AI and kubernetes supported app.
portainer.io/blog/portainer-3-0-is-comingReplying to @femtek@lemmy.blahaj.zone
Portainer was outdated 5 years ago, and it sucked at the job it did.
I’ma stick with dockge and argocd
Replying to @scottmeme@sh.itjust.works
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.
Replying to @wreckedcarzz@lemmy.world
For a lot of my remote hosted services managed with compose, I’ve just been hand rolling the compose files and ssh’ing in.
Replying to @scottmeme@sh.itjust.works
How do you detect outdated containers?
Replying to @northernlights@lemmy.today
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
Replying to @northernlights@lemmy.today
I was using the watchtower updater until it got archived, thankfully there is a maintained fork now
github.com/nicholas-fedor/watchtower
I still need to figure out a auto update solution for my Argo managed services
GitHubGitHub - nicholas-fedor/watchtower: Automate Docker container image updatesAutomate Docker container image updates. Contribute to nicholas-fedor/watchtower development by creating an account on GitHub.dockcheck
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.