Yeah, I used that for a bit before I found Poolsman. It’s nice but hasn’t been updated in a bit. I just went with Poolsman since it’s being actively developed (I just looked to confirm this and it appears 45Drives pushed out an update back in November of '23 which is nice, but nothing since then).
I agree, that’s all I’ve been saying (albeit in a very long winded fashion).
That’s always the problem, you can’t make everyone happy. I’d be more than content if there was a field that simply said “paste in a compose file and hit go”, while still retaining K3S for those that want to use it. Docker and Kubernetes are complex as it is, and occasionally difficult to debug issues. I just find that obfuscating that behind a middleware makes it 10x harder to debug and forces you to learn yet another thing just to accomplish what you set out to do originally.
Update on this… I spent the day yesterday dealing with this issue… it appears to be an IPv6 behaviour change in Docker…
I think I’ve resolved it…
Had rebooted back to Cobia… and for the last 24 hours its been good… Back on Dragonfish… with the lru_gen fix enabled… will see if its good… or if I need to revert back to Cobia again.
In all seriousness… after the VM being stable on Cobia for the last day… I rebooted into Dragonfish… and guess what… within a few hours… back to cobia…
I think I just discovered a solution that will appease @dan (and other users that feel the same way) and those of that just want docker-compose support: It’s called Yacht
It’s a small project and even though the dev says it’s alpha software and can be unstable I haven’t had any issues with it. It has a nice web UI which is themeable, and supports pretty much all the stuff that Dockge and Portainer do. The only things that are missing are console access to the containers and multi-user support.
You can use your own compose files, paste in ones via the UI, or utilize the the templates which allow for one-click deployments. There are already 4 catalogues available which amounts to at least 200 apps, and you can easily create a catalogue yourself for anything that is missing via another project called Shipwright which is a webUI where you enter in all the info for your desired templates, and then it will spit out an archive which contains Portainer v1 and v2 templates, along with one for Yacht. All you need to do in order to utilize your own catalogue is to create a git repo with the JSON file(s) and then add that JSON file to Yacht. To test it out, and since it was missing, I created a template for Caddy-Reverse-Proxy-Cloudflare and it works without issue.
I think this would be great for both communities, we get docker support with one click installs or compose support, and they get a spotlight on the project and more developers. The dev is planning on rewriting the project and has already created yacht-nuxt but I haven’t tried it out yet.
Well, it looks like iXSystems is just about to kill k3s (at least as a standard feature rather than a user-installed sandbox) and migrate to plain docker-compose.
I expect that the app catalogue will be dropped with 25.04.
App catalog isn’t going anywhere. That’s important for users who just want an easy button to install the most common of applications. We also use it for our Enterprise catalog.
If anything we’d expect the app catalog to keep growing at a much faster rate. Especially because the bar to entry will be so much lower to add new apps. Adding a compose-based App is so much less complicated than helm.
