#podman is not a drop-in replacement for #docker because it fails to keep pace with changes.
The average compose YAML has syntax podman-compose doesn't support. #redhat and contributors keep podman limping along but it's about time I move to systemd (or k8s) spec and stop fooling around with podman or compose at all.
I haven't been able to start #Nextcloud with #Collabora for months because of some random length limit issue related to seccomp.
@infinull is docker-compose more functional than podman-compose? In some cases where k8s seems like overkill or systemd isn’t around, it would be good to have something able to handle all composes. The problematic projects tend to be those that want to mount the socket and manage their own additional containers, and compose files that use substitution in the container/pod/namespace names.
I’ll try docker-compose with podman just ‘cuz. Thanks for the suggestion!
@andrew it's more compatible mainly. As you said the average compose file uses syntax podman-compose doesn't support.
I'm not using anything that mounts the docker/podman control socket.
I am using a wrapper to turn compose directories into systemd units.
Andrew Furrow
Mark Harviston