Debian Patches

Status for podman/5.8.4+ds1-2

Patch Description Author Forwarded Bugs Origin Last update
pkg-machine-platform.patch TestProviders: Skip test if unable to list providers
this is to fix autopkgtest in Debian when running in qemu		 Reinhard Tartler <siretart@tauware.de> no 2024-08-09
gopsutil-v4.patch Do not hardcode gopsutil v4

We can use v4 when no version suffix is used. Remove it so that we can
upgrade the gopsutil modules from v3 to v4 in Debian.		 Guillem Jover <gjover@sipwise.com> not-needed 2024-10-01
tests-system-skips.patch test/system: Skip some system tests that fail in Debian Reinhard Tartler <siretart@tauware.de> not-needed 2024-10-03
tests-integration-skips.patch e2e-test: Skip tests that don't currently work
These failures need to be investigated more closely		 Reinhard Tartler <siretart@tauware.de> no 2024-11-28
0006-Avoid-dependency-on-conmon-runner-config.patch Avoid dependency on conmon runner config Reinhard Tartler <siretart@tauware.de> not-needed 2025-09-18
0007-Allow-version-of-buildah-to-be-slightly-off.patch Allow version of buildah to be slightly off
When upstream is running these tests, they are guaranteed to be the same. In
Debian, the minor version might be slightly off without any issues		 Reinhard Tartler <siretart@tauware.de> no 2025-10-05
0007-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` (e.g., expecting
`containers-default-0.67.1`). 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.

This patch relaxes the Gomega assertion to simply check that the
`AppArmorProfile` field is not empty. This ensures we still validate
that Podman applies a profile, without tightly coupling the test to a
hardcoded version string.

These e2e tests are only executed as part of `autopkgtest`. Furthermore,
they are only run when using the `qemu` backend, because the tests
require the `isolation-machine` restriction to properly exercise container
isolation and AppArmor profiles.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-04-10
0008-Allow-searching-the-system-PATH-for-gvproxy.patch Allow searching the system PATH for gvproxy Reinhard Tartler <siretart@tauware.de> not-needed 2026-06-07
0009-Fix-build-failure-with-opencontainers-cgroups-0.0.6.patch Fix build failure with opencontainers-cgroups < 0.0.6
Restores compatibility of final.PidsLimit assignment with cgroups v0.0.5,
where PidsLimit is defined as an int64 rather than *int64.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-06-27
0010-podman-info-remove-storage.conf-path.patch podman info: remove storage.conf path
Given the new config file logic will read many files pritning one
specific one here has no meaning anymore, just delete it.		 Paul Holzinger <pholzing@redhat.com> no 2026-02-12
0011-podman-system-reset-do-not-print-storage.conf-warnin.patch podman system reset: do not print storage.conf warning
The orginal motivation was to give a hint to users to delete the file if
they did not create the storage.conf file since some early versions of
podman did auto generate that file[1].

However that was a really long time ago and with the config file rework
there can be many different storage.conf paths so this warning is no
longer useful so we should be able to remove this now.

[1] https://github.com/containers/podman/issues/7447		 Paul Holzinger <pholzing@redhat.com> no 2026-02-12
0012-system-service-remove-config-reload-functionallity.patch system service: remove config reload functionallity
As I outlined in the design docs this is broken, there are several
data races here because we write to the config files that can be read by
other goroutines in parallel which violates the go memory model and
thus can lead to runtime panics and undefined behavior.
One could fix with a mutex but that would make the whole code base much
more ugly and there is still the risk that something would access this
field without the mutex held.

I am not sure we have any users using this, it never worked for the
storage side and since the service is a not a daemon any user could just
stop and start it again to re-read the files without having to stop
running containers.		 Paul Holzinger <pholzing@redhat.com> no 2026-02-12
0013-cmd-podman-testing-drop-types.ReloadConfigurationFil.patch cmd/podman-testing: drop types.ReloadConfigurationFileIfNeeded
Upstream containers/storage v1.63.0 removed types.ReloadConfigurationFileIfNeeded.
Backport the upstream change from commit 78c28fc254d2 to drop this block and
its import from cmd/podman-testing/store_supported.go.		 Reinhard Tartler <siretart@tauware.de> not-needed 2026-08-18
0014-test-system-fix-empty-default-test.patch test/system: fix empty default test
We no longer generate a warning for an empty driver in storage.conf so
remove that.		 Paul Holzinger <pholzing@redhat.com> no 2026-03-06
0015-test-e2e-fix-podman-pull-and-run-on-split-imagestore.patch test/e2e: fix podman pull and run on split imagestore test
We no longer generate a warning for an empty driver in storage.conf so
remove that.

Also update the test to use CONTAINERS_STORAGE_CONF_OVERRIDE instead to
just add a single setting there.		 Paul Holzinger <pholzing@redhat.com> no 2026-03-09

All known versions for source package 'podman'

Links