|
|
|
|
|
|
by dns_snek
270 days ago
|
|
|
It works but it's not a real drop-in replacement in my experience. I have issues such as [1] where Podman compose seems to leave containers in a dirty state and subsequent `podman compose up` generate odd errors like: > Error: creating container storage: the container name "..." is already in use by [hash]. You have to remove that container to be able to reuse that name: that name is already in use, or use --replace to instruct Podman to do so. And then you try to run `podman compose up --replace` except that's not a recognized argument, so eventually you figure out that you have to run `podman compose down` to clean whatever state is causing issues. I find that I have to do that every time I CTRL+C quit out of `podman compose up` (even though I always let it clean up and then exit on its own), which is a hassle. I'm considering going back to using Docker Engine. [1] https://github.com/containers/podman-compose/issues/1072 |
|
|