Your message dated Fri, 13 Mar 2026 08:49:59 -0400
with message-id <[email protected]>
and subject line Re: Bug#1125400: podman: fails to generate dependency graph
with podman-compose
has caused the Debian Bug report #1125400,
regarding podman: fails to generate dependency graph with podman-compose
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1125400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125400
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: podman
Version: 5.4.2+ds1-2+b2
Severity: normal
X-Debbugs-Cc: [email protected]
Hi,
On debian 13, there is a known podman bug (see
https://github.com/containers/podman-compose/issues/921) that makes
podman-compose fails non-deterministically to start a system with
multiple dependencies.
This bug happens with both the podman-compose version shipped with
debian and with the latest version.
The bug is on podman side.
This is an important issue for users wanting to upgrade from debian 12
(where only compose was available, no quadlets) to debian 13.
For now, the only workarounds are 1. using quadlets and 2. using the
reference implementation (docker-compose) but this last solution is not
desirable as it requires activating the podman socket and sending a
potentially large context tarball to the daemon.
Would it be possible to either patch or upgrade podman on Debian 13 to
fix this issue?
Thanks for your work and best regards,
Leo.
--- End Message ---
--- Begin Message ---
Version: 5.7.0+ds2-3
Hi Léo,
Thank you for taking the time to report this issue. The root cause of
this non-deterministic failure was identified upstream and resolved in
commit 4120115c862a70db59d66dd339c9d42703b14fdb, which was subsequently
merged into the Podman 5.6.0 release.
This upstream fix has been incorporated into Debian in podman version
5.7.0+ds2-3, which is currently available in Debian testing. Because
this version contains the patched logic, I am marking this bug as
closed.
Could you please test this new version in testing to confirm that it
fully resolves the dependency graph issue for your compose environments?
I acknowledge your request to have this fixed in the stable release to
ensure a smooth upgrade path for users migrating from Debian 12. Please
note that the process for updating packages in stable requires the issue
to first be confirmed fixed and tested in testing. Furthermore, the
Debian Stable Release Managers maintain a very high bar for accepting
updates into a stable release; typically, only severe security
vulnerabilities or critical regressions are approved for stable updates.
I invite you to participate in evaluating whether this issue meets those
strict criteria for a Stable Release Update. I am personally not
convinced that it meets the bar for an update to stable at this time,
but I am happy to be convinced otherwise if you can help articulate the
broader impact and severity. Once you are able to verify the fix in
testing, we can discuss the justification further and decide whether to
formally propose the stable update.
Best regards,
-rt
--- End Message ---
