Debian Patches

Status for podman/6.1.1+ds1-1

Patch Description Author Forwarded Bugs Origin Last update
0001-TestProviders-Skip-test-if-unable-to-list-providers.patch TestProviders: Skip test if unable to list providers

In minimal Debian build environments and autopkgtest runners (such as
unprivileged chroots or container testbeds), optional machine provider
binaries (such as qemu-system-*) may not be installed. When
InstalledProviders() returns an error under these conditions, skip the
test rather than failing the build.		 Reinhard Tartler <siretart@tauware.de> not-needed 2024-08-09
0002-Do-not-hardcode-gopsutil-v4.patch Do not hardcode gopsutil v4

Upstream imports github.com/shirou/gopsutil/v4 explicitly via Go modules.
In Debian, golang-github-shirou-gopsutil-dev provides the module under
the unversioned github.com/shirou/gopsutil import path. Remove the /v4
suffix to allow building with Debian's packaged gopsutil.		 Guillem Jover <gjover@sipwise.com> not-needed debian 2024-10-01
0003-test-system-Skip-some-system-tests-that-fail-in-Debian.patch test/system: Skip some system tests that fail in Debian

Tag tests with 'debian_ignore' in the bats test suite:
- 'podman run --timeout - basic test': timing-sensitive test that is
flaky on loaded Debian buildd / autopkgtest infrastructure.
- 'podman exec - leak check': sensitive to inherited file descriptors
and environment variations in Debian test environments.

This allows Debian package testing to filter them out via
--filter-tags '!debian_ignore'.		 Reinhard Tartler <siretart@tauware.de> not-needed 2024-10-03
0004-test-e2e-Skip-host-limits-test-on-Debian.patch test/e2e: Skip host limits test on Debian

Upstream skips the 'podman run limits host test' on Debian only when
running rootless. However, in Debian autopkgtest runners the test also
fails in rootful mode with 'expected 1048576 to be >= 1073741816' due
to default system rlimit configurations. Skip this test unconditionally
on Debian distributions.		 Reinhard Tartler <siretart@tauware.de> not-needed 2024-11-28
0005-Allow-version-of-buildah-to-be-slightly-off.patch Allow version of buildah to be slightly off in e2e tests

Upstream assumes lockstep version matching between Podman and Buildah
due to vendoring. In Debian, golang-github-containers-buildah-dev is
packaged and updated independently, meaning minor version strings in
image build labels may vary slightly. Comment out the strict version
label check in test/e2e/build_test.go.		 Reinhard Tartler <siretart@tauware.de> not-needed 2025-10-05
0006-Relax-AppArmor-profile-check-in-e2e-tests.patch Relax AppArmor profile check in e2e tests

The upstream e2e tests for Podman use the Ginkgo testing framework and
Gomega matchers. The test for the default AppArmor profile previously
asserted an exact string match against apparmor.Profile. This causes
brittle test failures in Debian when the containers/common dependency is
updated independently or when there are minor version discrepancies
between the suite and the binary.

Relax the Gomega assertion to check that AppArmorProfile is not empty.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-04-10
0007-Allow-searching-the-system-PATH-for-gvproxy.patch Allow searching the system PATH for gvproxy

In upstream Podman, FindHelperBinary is called with matchPath=false for
the gvproxy forwarder binary, which restricts searches to internal helper
directories. In Debian, gvproxy is installed directly into /usr/bin. Set
matchPath=true so that Podman can discover gvproxy in standard system PATH.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-06-07
0008-test-system-parse-last-line-of-buildah-output-in-040.patch test/system: parse last line of buildah output in 040-ps

buildah from may emit warning messages to stdout/stderr in Debian test
environments (such as notices regarding storage driver defaults). In
test/system/040-ps.bats, capturing the entire $output into $buildah_cid
causes 'buildah commit $buildah_cid' to fail due to multiple words.

Use ${lines[-1]} to isolate the container name/ID from any preceding
warning logs, matching the pattern used for buildah_image_id.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-08-23
0009-test-system-align-globalargs-in-155-partial-pull-wit.patch test/system: align globalargs in 155-partial-pull with test 1

In test/system/155-partial-pull.bats, test 2 explicitly passed
--storage-driver $(podman_storage_driver). When Debian's storage.conf
leaves the storage driver unset (empty string for auto-detection),
the initial test store is created with graph driver "", which conflicts
with explicitly passing --storage-driver overlay ("database graph driver
\"\" does not match our graph driver \"overlay\": database configuration
mismatch").

Align test 2 with test 1 by omitting the redundant --storage-driver flag.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-08-23
0010-Disable-external-compose-provider-warning-by-default.patch Disable external compose provider warning by default

On Debian, podman-compose(1) is provided by the separate python
podman-compose source package to avoid file conflicts (#1054460). As a
result, the installed man page does not document compose_warning_logs
or PODMAN_COMPOSE_WARNING_LOGS. The warning emitted by 'podman compose'
directing users to podman-compose(1) is misleading and confusing
(#1141972).

Disable the external compose provider warning by default on Debian.		 Reinhard Tartler <siretart@tauware.de> not-needed debian 2026-08-25
0011-Revert-deps-bump-go-criu-to-v8.2.0.patch Revert "deps: bump go-criu to v8.2.0"
Debian currently packages go-criu v7 (7.2.0+ds1) in
golang-github-checkpoint-restore-go-criu-dev. Revert upstream commit
3c4068bcd6 to restore compatibility with go-criu/v7.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-09-08
0012-Restore-github.com-docker-docker-API-imports.patch Restore github.com/docker/docker API imports
Debian packages Docker API types in golang-github-docker-docker-dev under
github.com/docker/docker/api. Revert moby/moby imports to github.com/docker/docker
to allow building against Debian's docker.io packages (Docker 28.5).

Additionally, embed self-contained API models (jsonstream structs,
SystemDiskUsage and subsystem DiskUsage response structs, ExecCreateConfig,
ContainerSummary, PortSummary, HealthSummary, and InspectResponse) to match
Debian's Docker API without external dependencies.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-09-08
0013-Revert-runtime-spec-v1.3.0-changes-for-LinuxPids.Lim.patch Revert runtime-spec v1.3.0 changes for LinuxPids.Limit
In opencontainers/runtime-spec v1.3.0, LinuxPids.Limit was changed
from int64 to *int64. Since Debian unstable provides runtime-spec
v1.2.1, revert Podman's usage of pointer Limit to value Limit to
retain compatibility with runtime-spec v1.2.x.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-09-08

All known versions for source package 'podman'

Links