Bug#1059496: podman: network ls: might fail to handle removed container

2024-03-13 Thread Jérôme Charaoui 
Just for the record, I've submitted a debdiff that includes the upstream 
patch for to fix this as a proposed-update for bookworm:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066096

-- Jérôme

Bug#1059496: podman: network ls: might fail to handle removed container

2023-12-26 Thread Georg Faerber 
Package: podman
Version: 4.3.1+ds1-8+b1
Control: fixed -1 4.7.2+ds1-2
Severity: normal
Forwarded: https://github.com/containers/podman/issues/17341
Tags: bookworm fixed-upstream upstream 

podman 4.3.1+ds1-8+b1, as currently present in bookworm, might fail to
list a network while a container was just removed.

GitLab CI recently added the possibility to use podman as an executor,
instead of docker, and requires a feature flag 'FF_NETWORK_PER_BUILD' to
be set, see [1] for the upstream docs.

However, due to the above described problem, container preparation
initiated by podman might fail [2].

This was fixed in podman upstream [3] and released in 4.5.0.

Any chance this fix could be backported to bookworm via a
proposed-update? If helpful, I'm able to test a proposed, fixed package.

Thanks a lot for maintaining podman in Debian!

Cheers,
Georg


[1] 
https://docs.gitlab.com/runner/executors/docker.html#use-podman-to-run-docker-commands
[2] https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28971
[3] https://github.com/containers/podman/pull/17376