Repository navigation
Releases
Releases Β· podman-container-tools/podman
v6.2.0
Security
- Addresses CVE-2026-121885, untrusted image labels could be used to trick podman auto-update into restarting incorrect systemd units GHSA-55rm-rwr7-q2wr.
- Addresses CVE-2026-111361, malicious containers images could be able to bypass Digest and Signature validation GHSA-pggw-qqjf-6cxw.
- Addresses CVE-2026-123876, default seccomp profile socket deny rule could be bypass by a malicious container.
Features
- The
podman pushcommand now supports a new option,--platform, which selects and pushes a single platform-specific manifest instead of the entire list. - The
podman kube playcommand now supports a new option,--validate, which determines how unrecognized YAML fields are handled (#18332). - The
podman kube playcommand now supports a new option,--label, to set labels on created containers, pods, volumes, and secrets (#26450). - The
podman kube playcommand can now create multiple pods if more than 1 replica is requested by a deployment using the new--multiple-podsoption (#26769). - The
podman kube play --buildcommand now supports building images from subdirectories of the main context directory (#28148). - Quadlet
.containerfiles now support a new key,Umask, to set the default umask for the created container (#25278). - All Quadlet files now support a new key,
SetMountsDependency, configuring whether the generated unit will useRequiresMountsFor,WantsMountsFor, or no dependency at all on required source paths (#29946). - The
podman farm listcommand now supports two new options,--quiet, which will print only the names of active farms, and--noheading, which omits column headers from the output. - The
podman artifact lscommand now supports two new options,--format=json, which will output machine-readable JSON, and--quiet, which prints only artifact digests. - The
podman createcommand now supports a new option,--passwd, to add entries to/etc/passwdin the container (this has previously been available withpodman run). - The
podman infocommand now includes detailed information on the features supported by OCI runtimes. - The
podman events --filtercommand now supports a new filter,network=, to filter to events pertaining to a specific network (#29387). - The
podman auto-updatecommand has been enabled on the remote Podman client. - The
StartIntervalfield in image healthcheck configuration is now respected, allowing images to configure startup healthchecks (#27724). - The
podman image scpcommand now supports two new options,--compression-formatand--compression-level, to compress data during transfer (#23192). - The
podman auto-updatecommand now supports a new option,--filter, to selectively update only containers that match the given filters. - The
podman ps --sortcommand now allows sorting by pod. - The
podman ps --filtercommand now supports a new filter,status!, which matches containers not in the given state (#21398).
Changes
- Podman now requires Go v1.26 or higher to build.
- The Podman machine WSL provider now has native systemd support, existing machines continue to be supported for now with our old custom systemd setup. We require at least WSL version 2.5.1 now, although we recommend using at least 2.7.5 for proper nftables networking support.
- The
podman kube playcommand now uses thesecurityContext.seccompProfilefields in Kubernetes YAML for Seccomp configuration. Support for the existing annotation-based configuration of Seccomp is now deprecated, and will be removed with Podman 7.0. - The
podman inspectcommand on containers now includes three new fields,DNSNames(containing all names the container can be accessed via),IsInitCtr(whether the container is an init container), andInitContainerType(what type of init container this is, if it is one) (#29811). - The
podman inspectcommand on containers now only includes user-added DNS aliases in theAliasesfield, which previously displayed all DNS aliases, improving Docker compatibility. - The
podman inspectcommand on containers now properly populates theConsoleSizefield for running containers (#28368). - Systemd units created by Podman healthchecks are now named much more clearly (
libpod-healthcheck-$CONTAINERID-$randsuffix.service) (#29373). - Signal proxying is now enabled for attached
podman execcommands. As such, killing apodman execcommand with Control-C or similar should now also kill the processes started in the container (similar to howpodman runalready works) (#19486). - The deprecated
--cpu-rt-periodand--cpu-rt-runtimeoptions forpodman create,podman run,podman update, andpodman container cloneare now hidden and undocumented. They have not been functional since the removal of cgroups v1 support and will be removed entirely in Podman v7. - The
--health-startup-intervaloption topodman create,podman run, andpodman updatehas a new alias,--health-start-interval. - When a startup healthcheck interval is specified, but no startup healthcheck command, the standard healthcheck command will be used instead.
- When using the
journaldevent driver, timestamps are no longer included in logged events, asjournaldincludes a timestamp already (#29835). - Quadlet can now create template instances from instance-specific drop-in directories without requiring an explicit instance file or symlink (#27636).
Bugfixes
- Fixed a bug where passing an empty file to the
--ignorefileoption topodman buildwould cause the.dockerignoreor.containerignorefile in the context directory to be used, instead of not using an ignorefile at all (#25147). - Fixed a bug where the
Pod=key in Quadlet.containerfiles did not expand the%Nspecifier (#29108). - Fixed a bug where containers created with
--userns=autowould report having aprivateuser namespace inpodman inspectafter they started, but not when they were first created. - Fixed a bug where logging was configured too late in the Podman init process to print errors from parsing configuration files (#25362).
- Fixed a bug where the
podman system prune --buildcommand could fail if a build container was removed while it was running. - Fixed a bug where
copyevents frompodman machine cpwere not properly displayed by the remote Podman client. - Fixed a bug where the
podman farm build --tagcommand would fail if given a tag including a colon (#25039). - Fixed a bug where the
podman machine init --imagecommand would fail when given a read-only disk image. - Fixed a bug where the
podman machine startandpodman machine init --nowcommands could hang on Windows systems using the Hyper-V provider if the VM failed to start (#29455). - Fixed a bug where the
podman machine startcommand on Windows (both Hyper-V and WSL providers) would sometimes fail due to leftover processes from previous machines (#29474). - Fixed a bug where the
podman machine startcommand could hang indefinitely if the VM failed to start properly (#29880). - Fixed a bug where the
podman machine startcommand could create a VM that cannot be connected to on Windows if the host was shut down or restarted when the VM was running (#29971). - Fixed a bug where the
podman machine initcommand on Windows when using the Hyper-V provider did not correctly detach the file server process, causing VMs to lose access to host shares when the console that ranpodman machine initclosed (#29573). - Fixed a bug where the
podman kube playcommand incorrectly handledemptyDirvolumes withmedium: Memory, causing them to not be shared between containers in the pod and to ignore thesizeLimitparameter (#29555). - Fixed a bug where the remote Podman client's
podman kube playcommand incorrectly handled authentication credentials in API requests. - Fixed a bug where volumes created by the
podman volume importcommand would not adjust their permissions on being mounted into a container (#25442). - Fixed a...
v5.8.10
Security
- Addresses CVE-2026-121885, untrusted image labels could be used to trick podman auto-update into restarting incorrect systemd units GHSA-55rm-rwr7-q2wr.
- Addresses CVE-2026-111361, malicious containers images could be able to bypass Digest and Signature validation GHSA-pggw-qqjf-6cxw.
- Addresses CVE-2026-123876, default seccomp profile socket deny rule could be bypass by a malicious container.
v6.2.0-RC1
Features
- The
podman pushcommand now supports a new option,--platform, which selects and pushes a single platform-specific manifest instead of the entire list. - The
podman kube playcommand now supports a new option,--validate, which determines how unrecognized YAML fields are handled (#18332). - The
podman kube playcommand now supports a new option,--label, to set labels on created containers, pods, volumes, and secrets (#26450). - The
podman kube playcommand can now create multiple pods if more than 1 replica is requested by a deployment using the new--multiple-podsoption (#26769). - The
podman kube play --buildcommand now supports building images from subdirectories of the main context directory (#28148). - Quadlet
.containerfiles now support a new key,Umask, to set the default umask for the created container (#25278). - All Quadlet files now support a new key,
SetMountsDependency, configuring whether the generated unit will useRequiresMountsFor,WantsMountsFor, or no dependency at all on required source paths (#29946). - The
podman farm listcommand now supports two new options,--quiet, which will print only the names of active farms, and--noheading, which omits column headers from the output. - The
podman artifact lscommand now supports two new options,--format=json, which will output machine-readable JSON, and--quiet, which prints only artifact digests. - The
podman createcommand now supports a new option,--passwd, to add entries to/etc/passwdin the container (this has previously been available withpodman run). - The
podman infocommand now includes detailed information on the features supported by OCI runtimes. - The
podman events --filtercommand now supports a new filter,network=, to filter to events pertaining to a specific network (#29387). - The
podman auto-updatecommand has been enabled on the remote Podman client. - The
StartIntervalfield in image healthcheck configuration is now respected, allowing images to configure startup healthchecks (#27724). - The
podman image scpcommand now supports two new options,--compression-formatand--compression-level, to compress data during transfer (#23192). - The
podman auto-updatecommand now supports a new option,--filter, to selectively update only containers that match the given filters. - The
podman ps --sortcommand now allows sorting by pod. - The
podman ps --filtercommand now supports a new filter,status!, which matches containers not in the given state (#21398).
Changes
- Podman now requires Go v1.26 or higher to build.
- The
podman kube playcommand now uses thesecurityContext.seccompProfilefields in Kubernetes YAML for Seccomp configuration. Support for the existing annotation-based configuration of Seccomp is now deprecated, and will be removed with Podman 7.0. - The
podman inspectcommand on containers now includes three new fields,DNSNames(containing all names the container can be accessed via),IsInitCtr(whether the container is an init container), andInitContainerType(what type of init container this is, if it is one) (#29811). - The
podman inspectcommand on containers now only includes user-added DNS aliases in theAliasesfield, which previously displayed all DNS aliases, improving Docker compatibility. - The
podman inspectcommand on containers now properly populates theConsoleSizefield for running containers (#28368). - Systemd units created by Podman healthchecks are now named much more clearly (
libpod-healthcheck-$CONTAINERID-$randsuffix.service) (#29373). - Signal proxying is now enabled for attached
podman execcommands. As such, killing apodman execcommand with Control-C or similar should now also kill the processes started in the container (similar to howpodman runalready works) (#19486). - The deprecated
--cpu-rt-periodand--cpu-rt-runtimeoptions forpodman create,podman run,podman update, andpodman container cloneare now hidden and undocumented. They have not been functional since the removal of cgroups v1 support and will be removed entirely in Podman v7. - The
--health-startup-intervaloption topodman create,podman run, andpodman updatehas a new alias,--health-start-interval. - When a startup healthcheck interval is specified, but no startup healthcheck command, the standard healthcheck command will be used instead.
- When using the
journaldevent driver, timestamps are no longer included in logged events, asjournaldincludes a timestamp already (#29835). - Quadlet can now create template instances from instance-specific drop-in directories without requiring an explicit instance file or symlink (#27636).
Bugfixes
- Fixed a bug where passing an empty file to the
--ignorefileoption topodman buildwould cause the.dockerignoreor.containerignorefile in the context directory to be used, instead of not using an ignorefile at all (#25147). - Fixed a bug where the
Pod=key in Quadlet.containerfiles did not expand the%Nspecifier (#29108). - Fixed a bug where containers created with
--userns=autowould report having aprivateuser namespace inpodman inspectafter they started, but not when they were first created. - Fixed a bug where logging was configured too late in the Podman init process to print errors from parsing configuration files (#25362).
- Fixed a bug where the
podman system prune --buildcommand could fail if a build container was removed while it was running. - Fixed a bug where
copyevents frompodman machine cpwere not properly displayed by the remote Podman client. - Fixed a bug where the
podman farm build --tagcommand would fail if given a tag including a colon (#25039). - Fixed a bug where the
podman machine init --imagecommand would fail when given a read-only disk image. - Fixed a bug where the
podman machine startandpodman machine init --nowcommands could hang on Windows systems using the Hyper-V provider if the VM failed to start (#29455). - Fixed a bug where the
podman machine startcommand on Windows (both Hyper-V and WSL providers) would sometimes fail due to leftover processes from previous machines (#29474). - Fixed a bug where the
podman machine startcommand could hang indefinitely if the VM failed to start properly (#29880). - Fixed a bug where the
podman machine startcommand could create a VM that cannot be connected to on Windows if the host was shut down or restarted when the VM was running (#29971). - Fixed a bug where the
podman machine initcommand on Windows when using the Hyper-V provider did not correctly detach the file server process, causing VMs to lose access to host shares when the console that ranpodman machine initclosed (#29573). - Fixed a bug where the
podman kube playcommand incorrectly handledemptyDirvolumes withmedium: Memory, causing them to not be shared between containers in the pod and to ignore thesizeLimitparameter (#29555). - Fixed a bug where the remote Podman client's
podman kube playcommand incorrectly handled authentication credentials in API requests. - Fixed a bug where volumes created by the
podman volume importcommand would not adjust their permissions on being mounted into a container (#25442). - Fixed a bug where the
podman buildcommand could leak temporary directories if a build failed (#22642). - Fixed a bug where containers created with
--userns=keep-idwould use an image-specified user instead of forcing the same UID/GID in use on the host (#29600). - Fixed a bug where the remote Podman client could not function when connecting over SSH to a server which does not support the direct-streamlocal channel type (#27814).
- Fixed a bug where the remote Podman client's
podman push,podman artifact push, andpodman manifest pushcommands would push an unsigned image instead of failing when the--sign-byor--sign-by-sigstore-private-keyoptions were used. - Fixed a bug...
v6.1.4
Bugfixes
- Fixed an issue where Podman would not function when run under WSL 3 (#29749).
Misc
- Updated gvproxy to v0.9.0, resolving CVE-2026-107935
- Updated Buildah to v1.45.2
- Updated Storage to v1.64.2
v5.8.9
Bugfixes
- Fixed an issue where Podman would not function when run under WSL 3 (#29749).
- Fixed a bug with
podman machineVMs on Mac where machines could be left in an inconsistent state if thepodman machine startcommand was interrupted by a signal.
Misc
- Updated gvproxy to v0.9.0, resolving CVE-2026-107935
- Updated Buildah to v1.43.5
- Updated Storage to v1.62.2
v6.1.3
Security
- This release addresses CVE-2026-94603, where a
podman runon a checkpoint image (any image with theio.podman.annotations.checkpoint.runtime.nameannotation) could disable all sandboxing, including sandboxing specified by the user, when the container was created.
Breaking Changes
- Removed support for checkpoint images in
podman rundue to serious security concerns with the different security models of running images and running checkpoints. Checkpoints ignore user-specified security configuration and are very difficult to run safely.
v5.8.8
- This release addresses CVE-2026-94603, where a
podman runon a checkpoint image (any image with theio.podman.annotations.checkpoint.runtime.nameannotation) could disable all sandboxing, including sandboxing specified by the user, when the container was created.
Breaking Changes
- Removed support for checkpoint images in
podman rundue to serious security concerns with the different security models of running images and running checkpoints. Checkpoints ignore user-specified security configuration and are very difficult to run safely.
v5.8.7
Security
- This release addresses (CVE-2025-11395), where importing images containing crafted layer tarballs with the
podman loadcommand, or importing volumes containing crafted symlinks withpodman volume import, allows overwriting files on the host. - This release also addresses CVE-2026-79699 and CVE-2026-79705, though we do not believe these CVEs are exploitable through the Podman command line.
Misc
- Updated Buildah to v1.43.4
- Updated Common to v0.67.2
- Updated Image to v5.39.3
- Updated Storage to v1.62.1
v6.1.2
Security
- This release addresses (CVE-2025-11395), where importing images containing crafted layer tarballs with the
podman loadcommand, or importing volumes containing crafted symlinks withpodman volume import, allows overwriting files on the host. - This release also addresses CVE-2026-79699 and CVE-2026-79705, though we do not believe these CVEs are exploitable through the Podman command line.
Misc
- Updated Buildah to v1.45.1
- Updated Common to v0.69.2
- Updated Image to v5.41.2
- Updated Storage to v1.64.1
v6.1.1
Security
- This release addresses CVE-2026-17106, where a crafted tar archive could write outside the extraction directory through the use of malicious links (GHSA-hfg8-hc9c-6c3h).
Bugfixes
- Fixed broken rootlessport bind behavior with
-p 0.0.0.0:... -p [::]:...which failed instead of binding both v4 and v6 separately. Podman Machine on WSL should now correctly forward ports again by binding separate IPv4 and IPv6 sockets to make the WSL forwarder logic work again (#29377).