JsonDataError { message: "unknown variant stopped in ContainerStateStatusEnum with podman 4.4.2

[jiridanek]

let final_inspect = docker.inspect_container(&*container.id, Some(InspectContainerOptions { size: false })).await.unwrap();

thread 'testcontainers::test_h2spec::test_h2spec' panicked at 'called `Result::unwrap()` on an `Err` value: JsonDataError { message: "unknown variant `stopped`, expected one of ``, `created`, `running`, `paused`, `restarting`, `removing`, `exited`, `dead` at line 1 column 192", column: 192 }', tests/testcontainers/test_h2spec.rs:359:119

It looks like there is one additional state possible in

bollard/src/container.rs

Line 76 in a12c6b2

/// - `status`=(`created`|`restarting`|`running`|`removing`|`paused`|`exited`|`dead`)

bollard/codegen/swagger/src/models.rs

Lines 667 to 670 in a12c6b2

	/// String representation of the container state. Can be one of \"created\", \"running\", \"paused\", \"restarting\", \"removing\", \"exited\", or \"dead\".
	#[serde(rename = "Status")]
	#[serde(skip_serializing_if = "Option::is_none")]
	pub status: Option<ContainerStateStatusEnum>,

I am using bollard = "0.14.0" and podman version 4.4.2. I am starting podman with

systemctl --user enable --now podman.socket
export DOCKER_HOST=unix:///run/user/${UID}/podman/podman.sock

[fussybeaver]

Thanks for reporting.. There was a similar issue a while back: #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.

[jiridanek]

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

• https://docs.podman.io/en/latest/_static/api.html#tag/containers/operation/ContainerWaitLibpod
• https://docs.podman.io/en/latest/_static/api.html#tag/containers-(compat)/operation/ContainerWait

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

• https://github.com/moby/moby/blob/6f14c8ee5adc314a900808b0c991e12d9d28be67/api/swagger.yaml#L4629

So, could it be that the podman compat API is not compat enough?

[jiridanek]

Anyways, I'm going to raise this in podman as containers/podman#17728