Live data from Hacker News

Quadlets might make me finally stop using docker-compose

major.io

211–212 of 212 posts

Re: Quadlets might make me finally stop using docker-compose

#211
post #154

I don't see how this is anything like compose. With quadlets you have to create a file for each container and deal with creating volumes and so on. Whereas with Docker it's one file, one command and you're done, you don't have to deal with anything else.

They're both declarative manifests describing how to run one or more images on your system. You use .container for a single container, .kube for all-in-one pods, .network for networks, and .volume for volumes. It has all the stuff it's just broken down in a more (imho) sysadmin friendly way where all the pieces are independent and can be independently deployed.

How's that better? How many files do you need to replace a complex compose project, 10? And you still have to deal with SystemD?

Re: Quadlets might make me finally stop using docker-compose

#212

Earlier quoted context omitted.

Lolol have been running compose in dev & prod for 7 years - still the best tool around.

That might work for whatever you are doing, but the truth is that root-ful containers are not appropriate for a lot of applications, and docker as a layer to your container runtime is rough sometimes. I don't think docker wants to continue to develop this anyway - they have had enough problems trying to be profitable so instead it is time to focus on docker desktop and charging for docker hub image hosting. I feel li…

Docker already supports rootless, the issue is networking, which podman also suffers from.
Post reply on HN