Nicola Sella
Nicola Sella
cc: @jwhonce TL;DR: we are once again discussing `status` property exceptions when it's invoked after a `container.list` call
I would propose two approaches 1. `containers.list` calls `c.reload()` before `return` - https://github.com/containers/podman-py/commit/2c6806ba808d7f4dfb71080c67606a275c26cecc 2. `c.status` return "unknown" if `TypeError` - https://github.com/containers/podman-py/commit/fa92dd71d9a42f0e2801607fb895a52b3b17a58f
@l0rd sure, I can take it. I was actually briefly checking it this afternoon
@yusefkarim hey, thanks for picking it up. do you need help with the PR/unit tests?
/packit retest-failed
/packit build
@fulminemizzega thanks for the report. It shouldn't do that. The [client is initialized](https://github.com/containers/podman-py/blob/main/podman/tests/integration/test_containers.py#L29) on the testing sock, so all containers should be forcefully removed from the testing sock only Can...
yup, I can reproduce it. let me debug it
A note: The following example won't reproduce the issue ``` from podman import PodmanClient uri = "unix:///run/user/1000/podman/podman.sock" with PodmanClient(base_url=uri) as client: c = client.containers.run("nginx", remove=True, command="/bin/false") print(c.status) ``` while ```...
Ok, the problem is just that [detach](https://github.com/containers/podman-py/blob/main/podman/domain/containers_run.py#L70-L71) is called before [remove](https://github.com/containers/podman-py/blob/main/podman/domain/containers_run.py#L86-L87). I can see how the options can live together, but since I would avoid delegating the removal to the...