Disabling or removing a container may cause podman to hang

[troglobit]

Current Behavior

In a setup with two containers (see below), sometimes when temporarily disabling or removing one of the containers, podman may hang:

admin@example:/> show container 
CONTAINER ID  IMAGE                                                COMMAND     CREATED         STATUS         PORTS       NAMES
7a4c6252f574  localhost/curios-nftables-oci-amd64-v25.06.0:latest              13 seconds ago  Up 13 seconds              misc
16b8ec36a845  ghcr.io/kernelkit/curios:25.06.0                                 13 seconds ago  Up 13 seconds              sys101

admin@example:/> configure 
admin@example:/config/> set container sys101 enabled false
admin@example:/config/> leave
admin@example:/> show container 
CONTAINER ID  IMAGE                                                COMMAND     CREATED         STATUS         PORTS       NAMES
7a4c6252f574  localhost/curios-nftables-oci-amd64-v25.06.0:latest              29 seconds ago  Up 29 seconds              misc

admin@example:/> [wait a bit ...]
admin@example:/> show container 

The system just hangs there, fortunately Ctrl-C works, but there's no way to interact with the container sub-system, or even reboot the normal way. Only way to reboot is to exit back to the shell:

^C
root@infix-00-00-00:/> exit
root@infix-00-00-00:~$ reboot -f 
...

Expected Behavior

Podman should not hang.

Steps To Reproduce

See above, and example container configuration below.

Additional information

In interfaces I have a docker0 bridge. Set up according to the documentation:

  "ietf-interfaces:interfaces": {
    "interface": [
      {
        "name": "docker0",
        "type": "infix-if-type:bridge",
        "infix-interfaces:container-network": {
          "type": "bridge"
        }
      },

The container configuration looks like this

  "infix-containers:containers": {
    "container": [
      {
        "name": "misc",
        "image": "oci-archive:/lib/oci/curios-nftables-latest.tar.gz",
        "privileged": true,
        "network": {
          "host": true
        }
      },
      {
        "name": "sys101",
        "image": "docker://ghcr.io/kernelkit/curios:25.06.0",
        "hostname": "sys101",
        "network": {
          "interface": [
            {
              "name": "docker0"
            }
          ]
        },
        "volume": [
          {
            "name": "var",
            "target": "/var"
          }
        ]
      }
    ]
  },

From the shell, we can see with the ps command that something's running in the background, which looks like some housekeeper task that is started after Infix has called podman sys101 stop:

 4403 root      0:00 /usr/bin/podman --root /var/lib/containers/storage --runroot /run/containers/storage --log-level warning --cgroup-manager cgroupfs --tmpdir /run/libpod --network-config-dir  --network-backend cni --volumepath /var/lib/containers/storage/volumes --db-backend boltdb --transient-store=false --runtime crun --events-backend file container cleanup 480ddb4d0d394cb21e62069f777505b6c3b7e4cbe0f6df66a291c39fff6f8759

Attaching with strace -p 4403 only shows that the process is stuck on a "futex" of some kind.