Latest Docker Compose (v2)
https://docs.docker.com/compose/cli-command/
Now, the command is no longer docker-compose
(although there is compose-switch), but rather, a Docker plugin, docker compose
.
For some reasons, it had to rebuild my Dockerfile image again, even though I have built (and tagged) it before.
I saw that there that are releases for Windows and macOS (darwin, including arm64) as well; and it is already installed by default on Windows and macOS.
Legacy Docker Compose (v1)
https://docs.docker.com/compose/install/
This one has absolutely my expected behavior. Nothing special. No surprise dangers.
podman-compose
This one uses podman, which is probably only available in Linux (and macOS), and requires podman.service
user unit; so, probably cannot be started in Windows' WSL.
Goodies, other than can be rootless podman (i.e. no root privileges, nor usermod -aG docker $USER
); is that it actually create a "pod" containing multiple containers.
So, what are unexpected behaviors I have found?
- Cannot attach to virtual volumes, nor attach to non-existent folders (will not create a new folder)
-
podman-compose up $SERVICE_NAME
does not work, unlikedocker-compose
-
Ctrl+C
does not destroy pod, nor "down", sopodman-compose up
>>Ctrl+C
>>podman-compose up
will give some friendly(?) errors- In contrast,
docker-compose up
>>Ctrl+C
>>docker-compose up
throws no error; also noticeably, logs continue (just likeCtrl+X
>>kill -CONT
)
- In contrast,
Conclusion
So, is Podman better than Docker, or is Docker itself getting better than alternatives?
Top comments (1)
Nice article, this might be worth a look github.com/WMRamadan/docker-compos...