Docker is so bad. I don’t think a lot of you young bloods understand that. The system is so incredibly fragmented. Tools like Portainer are great, but they’re a super pain in the ass to use with tools/software that include a dockerfile vs a compose file. There’s no interoperability between the two which makes it insurmountably time-consuming and stupid to deal with certain projects because they’re made for a specific build environment which is just antithetical to good computing.
Like right now, I have Portainer up. I want to test out Coolify. I check out templates? Damn, not there. Now I gotta add my own template manually. Ok, cool. Half way done. Oops. It expects a docker-compose.yml. The Coolify repository only has a Dockerfile. Damn, now I have to make a custom template. Oh well, not a big deal. Plop in the Dockerfile from the repository, and click “deploy.” OOPS! ERROR: “failed to deploy a stack: service “soketi” has neither an image nor a build context specified: invalid compose project.” Well fuck… Ok, whatever. Not the biggest of deals. Let me search for an image of “soketi” using dockerhub. Well fuck. There are 3 images which haven’t been updated in several years. Awesome. Which one do I need? The echo-server? The network-watcher? PWS?
Like, do you see the issue here? There’s nothing about docker that’s straightforward at all. It fails in so many aspects it’s insane that its so popular.
Maybe I’m an idiot (high possibility) but I couldn’t even get the instance of homebridge docker to work. However, it had zero problems running on hypervisor. You aren’t alone.
I’m coming to appreciate Hyper-V more and more to be honest. It’s a very mature virtualization environment. The only issue I have with it is the inability to do GPU-passthrough. Once they figure that one out, I probably won’t bother with anything else.
Docker is so bad. I don’t think a lot of you young bloods understand that. The system is so incredibly fragmented. Tools like Portainer are great, but they’re a super pain in the ass to use with tools/software that include a dockerfile vs a compose file. There’s no interoperability between the two which makes it insurmountably time-consuming and stupid to deal with certain projects because they’re made for a specific build environment which is just antithetical to good computing.
Like right now, I have Portainer up. I want to test out Coolify. I check out templates? Damn, not there. Now I gotta add my own template manually. Ok, cool. Half way done. Oops. It expects a docker-compose.yml. The Coolify repository only has a Dockerfile. Damn, now I have to make a custom template. Oh well, not a big deal. Plop in the Dockerfile from the repository, and click “deploy.” OOPS! ERROR: “failed to deploy a stack: service “soketi” has neither an image nor a build context specified: invalid compose project.” Well fuck… Ok, whatever. Not the biggest of deals. Let me search for an image of “soketi” using dockerhub. Well fuck. There are 3 images which haven’t been updated in several years. Awesome. Which one do I need? The echo-server? The network-watcher? PWS?
Like, do you see the issue here? There’s nothing about docker that’s straightforward at all. It fails in so many aspects it’s insane that its so popular.
Docker got popular because of dockerfiles. It really sucks at service management though which is why people run Kubernetes in production, not Docker.
Maybe I’m an idiot (high possibility) but I couldn’t even get the instance of homebridge docker to work. However, it had zero problems running on hypervisor. You aren’t alone.
I’m coming to appreciate Hyper-V more and more to be honest. It’s a very mature virtualization environment. The only issue I have with it is the inability to do GPU-passthrough. Once they figure that one out, I probably won’t bother with anything else.