Debian Package Tracker
Register | Log in
Subscribe

podman

tool to manage containers and pods

Choose email to subscribe with

general
  • source: podman (main)
  • version: 5.6.2+ds1-1
  • maintainer: Debian Go Packaging Team (archive) (DMD)
  • uploaders: Reinhard Tartler [DMD] – Faidon Liambotis [DMD] – Dmitry Smirnov [DMD]
  • arch: any
  • std-ver: 4.7.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • stable: 5.4.2+ds1-2
  • testing: 5.6.1+ds2-3
  • unstable: 5.6.2+ds1-1
versioned links
  • 5.4.2+ds1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 5.6.1+ds2-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 5.6.2+ds1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • podman (8 bugs: 0, 5, 3, 0)
  • podman-docker
  • podman-remote
action needed
Marked for autoremoval on 05 November due to docker.io: #1115952 high
Version 5.6.1+ds2-3 of podman is marked for autoremoval from testing on Wed 05 Nov 2025. It depends (transitively) on docker.io, affected by #1115952. You should try to prevent the removal by fixing these RC bugs.
Created: 2025-09-29 Last update: 2025-10-05 17:00
1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:
  • CVE-2025-4953: A flaw was found in Podman. In a Containerfile or Podman, data written to RUN --mount=type=bind mounts during the podman build is not discarded. This issue can lead to files created within the container appearing in the temporary build context directory on the host, leaving the created files accessible.
Created: 2025-09-05 Last update: 2025-10-04 23:55
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2025-4953: A flaw was found in Podman. In a Containerfile or Podman, data written to RUN --mount=type=bind mounts during the podman build is not discarded. This issue can lead to files created within the container appearing in the temporary build context directory on the host, leaving the created files accessible.
Created: 2025-09-05 Last update: 2025-10-04 23:55
lintian reports 1 warning normal
Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.
Created: 2025-10-05 Last update: 2025-10-05 04:31
debian/patches: 2 patches to forward upstream low

Among the 6 debian patches available in version 5.6.2+ds1-1 of the package, we noticed the following issues:

  • 2 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2024-09-17 Last update: 2025-10-05 09:01
2 low-priority security issues in trixie low

There are 2 open security issues in trixie.

2 issues left for the package maintainer to handle:
  • CVE-2025-4953: (needs triaging) A flaw was found in Podman. In a Containerfile or Podman, data written to RUN --mount=type=bind mounts during the podman build is not discarded. This issue can lead to files created within the container appearing in the temporary build context directory on the host, leaving the created files accessible.
  • CVE-2025-9566: (needs triaging) There's a vulnerability in podman where an attacker may use the kube play command to overwrite host files when the kube file container a Secrete or a ConfigMap volume mount and such volume contains a symbolic link to a host file path. In a successful attack, the attacker can only control the target file to be overwritten but not the content to be written into the file. Binary-Affected: podman Upstream-version-introduced: v4.0.0 Upstream-version-fixed: v5.6.1

You can find information about how to handle these issues in the security team's documentation.

Created: 2025-09-05 Last update: 2025-10-04 23:55
testing migrations
  • This package will soon be part of the auto-gpgme1.0 transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
  • excuses:
    • Migration status for podman (5.6.1+ds2-3 to 5.6.2+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ autopkgtest for autopkgtest/5.51: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for cockpit-podman/114-1: amd64: Pass, arm64: Test triggered, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for debcraft/0.5.0: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for golang-github-containers-buildah/1.41.4+ds1-3: amd64: Pass, arm64: Test triggered, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for golang-github-containers-psgo/1.9.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for podman/5.6.2+ds1-1: amd64: Regression ♻ (reference ♻), arm64: Test triggered, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for podman-compose/1.5.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ autopkgtest for python-podman/5.4.0.1-3: amd64: Pass, arm64: Test triggered, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for rust-repro-env/0.4.3-2: amd64: Pass, arm64: Test triggered, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ autopkgtest for skopeo/1.20.0+ds1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Too young, only 0 of 5 days old
    • Additional info:
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/podman.html
    • ∙ ∙ Reproducible on amd64 - info ♻
    • ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻
    • Not considered
news
[rss feed]
  • [2025-10-04] Accepted podman 5.6.2+ds1-1 (source) into unstable (Reinhard Tartler)
  • [2025-09-30] podman 5.6.1+ds2-3 MIGRATED to testing (Debian testing watch)
  • [2025-09-28] podman 5.6.1+ds2-2 MIGRATED to testing (Debian testing watch)
  • [2025-09-27] Accepted podman 5.6.1+ds2-3 (source) into unstable (Reinhard Tartler)
  • [2025-09-21] Accepted podman 5.6.1+ds2-2 (source) into unstable (Reinhard Tartler)
  • [2025-09-21] Accepted podman 5.6.1+ds1-2 (source) into unstable (Reinhard Tartler)
  • [2025-09-10] Accepted podman 5.6.1+ds1-1 (source) into experimental (Reinhard Tartler)
  • [2025-07-14] podman 5.4.2+ds1-2 MIGRATED to testing (Debian testing watch)
  • [2025-07-08] Accepted podman 5.4.2+ds1-2 (source) into unstable (Mathias Gibbens)
  • [2025-04-08] podman 5.4.2+ds1-1 MIGRATED to testing (Debian testing watch)
  • [2025-04-05] Accepted podman 5.4.2+ds1-1 (source) into unstable (Reinhard Tartler)
  • [2025-04-04] podman 5.4.1+ds1-3 MIGRATED to testing (Debian testing watch)
  • [2025-04-01] Accepted podman 5.4.1+ds1-3 (source) into unstable (Reinhard Tartler)
  • [2025-03-30] podman 5.4.1+ds1-2 MIGRATED to testing (Debian testing watch)
  • [2025-03-27] Accepted podman 5.4.1+ds1-2 (source) into unstable (Reinhard Tartler)
  • [2025-03-27] podman 5.4.1+ds1-1 MIGRATED to testing (Debian testing watch)
  • [2025-03-20] Accepted podman 5.4.1+ds1-1 (source) into unstable (Reinhard Tartler)
  • [2025-03-08] podman 5.4.0+ds1-1 MIGRATED to testing (Debian testing watch)
  • [2025-02-16] Accepted podman 5.4.0+ds1-1 (source) into unstable (Reinhard Tartler)
  • [2025-01-30] podman 5.3.2+ds1-1 MIGRATED to testing (Debian testing watch)
  • [2025-01-27] Accepted podman 5.3.2+ds1-1 (source) into unstable (Reinhard Tartler)
  • [2024-12-13] podman 5.3.1+ds1-7 MIGRATED to testing (Debian testing watch)
  • [2024-12-10] Accepted podman 5.3.1+ds1-7 (source) into unstable (Reinhard Tartler)
  • [2024-12-09] podman 5.3.1+ds1-6 MIGRATED to testing (Debian testing watch)
  • [2024-12-06] Accepted podman 5.3.1+ds1-6 (source) into unstable (Reinhard Tartler)
  • [2024-12-06] podman 5.3.1+ds1-4 MIGRATED to testing (Debian testing watch)
  • [2024-12-05] Accepted podman 5.3.1+ds1-5 (source) into unstable (Reinhard Tartler)
  • [2024-12-02] Accepted podman 5.3.1+ds1-4 (source) into unstable (Reinhard Tartler)
  • [2024-12-01] Accepted podman 5.3.1+ds1-3 (source) into unstable (Reinhard Tartler)
  • [2024-12-01] podman 5.3.1+ds1-1 MIGRATED to testing (Debian testing watch)
  • 1
  • 2
bugs [bug history graph]
  • all: 7 8
  • RC: 0
  • I&N: 5
  • M&W: 2 3
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian (0, 1)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 5.4.2+ds1-2
  • 2 bugs

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing