As pointed out by Andreas offline, we should indeed verify this bug. I filled the SRU paperwork.
** Description changed: - n + [ Impact ] + + Both docker.io-app and podman-docker packages ship a /usr/bin/docker + file. Docker.io does not include a conflicts relation with podman- + docker, but podman-docker includes that relation (Conflicts/Replaces + docker.io/docker-cli). + + apt/apt-get behaves correctly in all supported releases when installing + one package over the other. Therefore, there is no greater impact here + unless the user (as happened with the original report) decides to use a + custom podman-docker package build without the Conflics/Replaces + relation. + + In other words, this bug does not really affect regular usage of these + packages for stable releases. Nevertheless, we are backporting this fix + to plucky/noble/jammy with the next container stack backport batch for + correctness. + + [ Test Plan ] + + Install docker.io. + Install podman-docker. + Verify that the package was correctly installed and docker.io was removed. + + Install podman-docker + Install docker.io + Verify that the package was correctly installed and podman-docker was removed. + + [ Where problems could occur ] + + This adds a new Conflicts/Replaces relation in the package. Unless new + packages providing the conflicting capabilites in the archive (and only + in the case the new capabilities are not really conflicting), + regressions should be checked elsewhere first. Otherwise, reverting this + change should be straightforward and should be generally OK given the + other conflicting counterpart already carries the relation. + + [ Other Info ] + + As mentioned by Julian in the comments, the new apt solver will protect + manually installed packages against removals due to Conflicts/Breaks + (when not using apt-get). Users using the new solver will still face an + issue when trying to replace one of the packages, but the error message + should include a good explanation of the conflict. Users should wither + remove the conflicting package in the same install operation (using a + "-") or use apt-get. ATM, this only applies to Ubuntu >= 25.10 + + [ Original Message ] ProblemType: Package DistroRelease: Ubuntu 22.04 Package: docker.io (not installed) ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Sep 24 18:01:40 2023 ErrorMessage: tentative de remplacement de « /usr/bin/docker », qui appartient aussi au paquet podman-docker 4:4.6.2-0ubuntu22.04+obs81.12 InstallationDate: Installed on 2022-11-19 (316 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: - dpkg 1.21.1ubuntu2.2 - apt 2.4.10 + dpkg 1.21.1ubuntu2.2 + apt 2.4.10 SourcePackage: docker.io-app Title: package docker.io (not installed) failed to install/upgrade: tentative de remplacement de « /usr/bin/docker », qui appartient aussi au paquet podman-docker 4:4.6.2-0ubuntu22.04+obs81.12 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037905 Title: package docker.io (not installed) failed to install/upgrade: tentative de remplacement de « /usr/bin/docker », qui appartient aussi au paquet podman-docker 4:4.6.2-0ubuntu22.04+obs81.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2037905/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
