Hacker News Reader

Comment by szastamasta | Hacker News Reader

Great news. I hope it will now work with docker compose. Missing compose support was the only reason I had to ditch it in favor of Colima. But will try it out again now.

View on HN

docker-compose was really the paradigm shift I needed when it came to containers and now I'm whole-heartedly on board with containerization. No reason something like the compose syntax (or similar) couldn't be a common, shared front-end to all container solutions, but until that point, I'm going to be sticking with Docker purely for certainty that docker-compose functions as expected.

Yes, but it's not the final solution. For example docker and docker-compose don't support composition. There's a market opportunity for something better. I thought it might be Nix, but seems to have not caught on.

The spec finally supports the extends keyword, to build upon another service in another file. But maybe this isn't what you meant by composition?

> No reason something like the compose syntax (or similar) couldn't be a common, shared front-end to all container solutions

Hopefully it will, since the docker-compose spec is being formalized: https://github.com/compose-spec/compose-spec

I use it with docker-compose now and I'm running podman 3.4.4. I think you just need to install `podman-docker` on Fedora to get the docker socket. See: https://www.redhat.com/sysadmin/podman-docker-compose.

`docker-compose` is different from `docker compose` (with a space in between words).

The former will be replaced by the latter in the long run.

https://github.com/docker/compose-cli/issues/901#issuecommen...

Oh! I thought it was just a typo. That is very unfortunate naming.

There is a shim so that they can be the same. The new docker compose (with space) is compatible with the old one.

Reply on news.ycombinator.com