Closed jiridanek closed 1 year ago
Thanks for reporting.. There was a similar issue a while back: https://github.com/fussybeaver/bollard/issues/238
The thread concluded that these differences are resolved with their podman compat layer.. can you check if that works for you? Would be good to put the solution down in the README somewhere.
I thought I'm using the compat API when I point bollard to the podman.sock. I don't really see what else I could be using, since bollard knows nothing about the libpod versions.
Anyways, looking at
it appears that both APIs have stopped
state in there.
When I look at the podman issue created for #238, there I see link to the moby API, which does not seem to have stopped in there
So, could it be that the podman compat API is not compat enough?
Anyways, I'm going to raise this in podman as https://github.com/containers/podman/issues/17728
It looks like there is one additional state possible in
https://github.com/fussybeaver/bollard/blob/a12c6b21b737e5ea9e6efe5f0128d02dc594f9aa/src/container.rs#L76
https://github.com/fussybeaver/bollard/blob/a12c6b21b737e5ea9e6efe5f0128d02dc594f9aa/codegen/swagger/src/models.rs#L667-L670
I am using bollard = "0.14.0" and podman version 4.4.2. I am starting podman with