Your message dated Sat, 27 Sep 2025 14:38:12 +0000
with message-id <[email protected]>
and subject line Bug#1115347: fixed in podman 5.6.1+ds2-3
has caused the Debian Bug report #1115347,
regarding podman: Please add a warning that upgrading from Bookworm to Trixie 
may break user containers due to new default rootless network "pasta"
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.)


-- 
1115347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115347
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: podman
Version: 5.4.2+ds1-2+b1
Severity: normal

Dear Maintainer,

I upgraded one of my Debian machines to Trixie and ran into some unexpected 
difficulties with podman. These were not mentioned in the Trixie release notes 
or the package's NEWS.Debian file.

1) After the upgrade, I noticed that my rootless user containers wouldn't start 
anymore. It turned out that podman couldn't find the command pasta. Now you 
could argue that this is a non-default setup that doesn't have all recommended 
packages installed. But the release notes have such warnings for other packages 
that may break if recommended packages aren't installed (e.g. 
systemd-cryptsetup or linux-sysctl-default).

2) But more importantly, even if you install the passt package, the new network 
command introduces breaking changes to rootless user containers - namely, they 
cannot communicate with the host anymore by default. I run a reverse proxy on 
the host that the containers need to reach, so none of my containers were 
accessible anymore with the change to pasta. I think this should be documented 
better to avoid unnecessary headaches for other podman users upgrading from 
Bookworm. While I found this [1] explanation online, it would have been much 
easier or less time-consuming, if it was mentioned in the NEWS.Debian file.

[1] https://blog.podman.io/2024/03/podman-5-0-breaking-changes-in-detail/


Hence, I recommend to add a user-visible warning about the pitfalls that come 
with pasta as the new network driver for rootless user containers.


Thanks and regards,


Timo

--- End Message ---
--- Begin Message ---
Source: podman
Source-Version: 5.6.1+ds2-3
Done: Reinhard Tartler <[email protected]>

We believe that the bug you reported is fixed in the latest version of
podman, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reinhard Tartler <[email protected]> (supplier of updated podman package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 25 Sep 2025 05:46:01 -0400
Source: podman
Architecture: source
Version: 5.6.1+ds2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<[email protected]>
Changed-By: Reinhard Tartler <[email protected]>
Closes: 1102908 1115347 1115941
Changes:
 podman (5.6.1+ds2-3) unstable; urgency=medium
 .
   * integration-tests-rootful: use $SUDO substitution to fix autopkgtest
   * podman: remove libpod.conf, 87-podman-bridge.conflist on upgrade,
     Closes: #1102908, #1115941
   * Add a NEWS entry for breaking changes in version 5.0.0, Closes: #1115347
Checksums-Sha1:
 d28b24b5a6c384262ebaa4647921a436345e804d 4721 podman_5.6.1+ds2-3.dsc
 8992defe2eca0b792f5a3f0148ca9d89b8213348 30584 podman_5.6.1+ds2-3.debian.tar.xz
Checksums-Sha256:
 37475ac5d06099b730a07c1447ef5472973053b80348bf86a60a981eb98dba2d 4721 
podman_5.6.1+ds2-3.dsc
 e36822782faabde94e823c6b06277c8653666ede91fc281a2e59c016a870acca 30584 
podman_5.6.1+ds2-3.debian.tar.xz
Files:
 4650b8b41dfd08f21b56889f193aaa7a 4721 admin optional podman_5.6.1+ds2-3.dsc
 999a7f754206b4394da74c779ece5e1e 30584 admin optional 
podman_5.6.1+ds2-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmjX7ccUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJss1yRAAqrY+zmoF9bpyOWtusexLTcutL+eu
q0HUT8qDD9LKamxDJOdsob+ege4n+1kOWphntOyW1bglok7MJVb044K0Q0+ZxW4R
sZeN66O+4ZfgfvU8E97D4V7KuGlIuRLA5XvyovEgQoYCdKJ/7pIP+ZExnviz9LWx
E6ENtnOwDIvMepQXlQvua/0xqYhkvE7DSnC0cYB/4I24CvZRf2VahYdZfci25ngL
6xRPik7v4Y2/XN/YHGRzZf4qkujM4YLl5bfR34f9g3sX1+cql2Uecw0na20iJ8J7
yL08/mx1F9Z/fUzSd0QNWVo1ia/qju+amcgPPZ438mrKUvC60fJzEScXWhCVEfps
Tj44P3XxddvcnaHA0UeyHeUBYwRVifj9KM8v2Z+XDv6wD7kNPJpQI01Yi2u4laFG
0kNLuBgr/isk940+oFbhGw19qrJ96wA+2aLRPe3N3QjWW8vgOvSNTNHD8zrXmH2D
1zQB1e63tVa0q/6vFg334jhs1snscRyf6v22tqsgeg1Ddq8mTO3WA9V7fgHDIRKU
rlb8hxixDAqdBv2OY/dgVst8SgBYaVco4gfQQa4NSO2a/ne+6DoG7foZfe9y2oKu
YhwXwD+MEeTSLPO+otG+HpZIZN0ESLuriKSHmJ0B37FhKPDEdjBAYhTsxCpIoFnh
iXioqZPtXiNIbHw=
=IsUc
-----END PGP SIGNATURE-----

Attachment: pgpYKp9PNeMS9.pgp
Description: PGP signature


--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to