# Podman changelog

> A daemonless container engine for OCI containers.

- Vendor: Red Hat
- Category: Developer Tools
- Official site: https://podman.io
- Tracked by: What's New (https://whatsnew.fyi/product/podman)
- Harvested from: GitHub (containers/podman)
- Entries below: 10 (newest first)

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

## Releases

### v6.1.0-rc1 — v6.1.0-RC1

- Date: 2026-07-31
- Version: v6.1.0-rc1
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v6.1.0-rc1
- Permalink: https://whatsnew.fyi/product/podman/releases/v6.1.0-rc1
- Labels: Pre-release

- **added** — Add podman volume rename command to allow renaming volumes
- **added** — Add podman machine restart command to allow easy restart of VMs managed by podman machine
- **added** — Add --ignore option to podman network rm command to suppress errors when attempting to remove networks that do not exist
- **added** — Add --retry and --retry-delay options to podman manifest push command to allow pushes to be automatically retried on failure
- **added** — Add ImageVolume= key support to Quadlet .container units to configure how volumes from images are handled
- **added** — Add support for generating container healthchecks as a livenessProbe in podman generate kube command
- **changed** — podman info command now includes free memory available on the host in addition to used memory and total memory
- **changed** — Pesto rootless port forwarding tool now supports IPv6 port forwarding with source IP preservation
- **fixed** — Fix remote Podman client hanging on some operations when connecting to a remote Podman service over SSH
- **fixed** — Fix podman image scp command not working with usernames containing an @ character
- **fixed** — Fix podman kube play command not properly validating requested hostPort bindings
- **fixed** — Fix podman machine VMs on Windows with hyperv provider sometimes not properly starting due to a race condition setting up volume mounts
- **fixed** — Fix podman machine VMs on Mac where machines could be left in an inconsistent state if podman machine start command was interrupted by a signal
- **fixed** — Fix podman machine on Mac returning a nonsensical error message when creating a container that attempts to bind to a port number below 1024
- **fixed** — Fix podman quadlet list and podman quadlet rm commands not functioning properly with uninstantiated template Quadlets
- **fixed** — Fix podman quadlet install command occasionally failing to install a Quadlet if non-quadlet files were specified
- **fixed** — Fix podman volume prune --all command incorrectly discarding label filters
- **fixed** — Fix podman events --format=json command printing null instead of an error when the server sent an event that could not be decoded
- **fixed** — Fix race condition causing Quadlet to generate corrupt systemd units

###### Features
- A new command has been added, `podman volume rename`, to allow renaming volumes. Volumes created using volume drivers and volumes that are currently used by a container cannot be renamed ([#28189](https://github.com/podman-container-tools/podman/issues/28189)).
- A new command has been added, `podman machine restart`, to allow easy restart of VMs managed by `podman machine` ([#28366](https://github.com/podman-container-tools/podman/issues/28366)).
- The `podman network rm` command now includes a new option, `--ignore`, which suppresses errors when attempting to remove networks that do not exist ([#28363](https://github.com/podman-container-tools/podman/issues/28363)).
- The `podman manifest push` command now includes two new options, `--retry` and `--retry-delay`, which allow pushes to be automatically retried on failure ([#28590](https://github.com/podman-container-tools/podman/issues/28590)).
- Quadlet `.container` units now support a new key, `ImageVolume=`, to configure how volumes from images are handled ([#28875](https://github.com/podman-container-tools/podman/issues/28875)).
- The `podman generate kube` command now includes support for generating container healthchecks as a `livenessProbe` ([#22095](https://github.com/podman-container-tools/podman/issues/22095)).

###### Changes
- The `podman info` command now includes free memory available on the host (in addition to used memory and total memory) ([#29116](https://github.com/podman-container-tools/podman/issues/29116)).
- The Pesto rootless port forwarding tool now supports IPv6 port forwarding with source IP preservation.

###### Bugfixes
- Fixed a bug where the remote Podman client could hang on some operations when connecting to a remote Podman service over SSH ([#28453](https://github.com/podman-container-tools/podman/issues/28453)).
- Fixed a bug where the `podman image scp` command could not be used with usernames containing an `@` character ([#27655](https://github.com/podman-container-tools/podman/issues/27655)).
- Fixed a bug where the `podman kube play` command did not properly validate requested `hostPort` bindings, allowing the creation of containers with duplicated host ports which would never be able to start at the same time ([#26622](https://github.com/podman-container-tools/podman/issues/26622)).
- Fixed a bug where `podman machine` VMs on Windows created using the `hyperv` provider would sometimes not properly start due to a race conditioning setting up volume mounts.
- Fixed a bug where `podman machine` VMs on Mac where machines could be left in an inconsistent state if the `podman machine start` command was interrupted by a signal.
- Fixed a bug where creating a container on a `podman machine` VM on Mac that attempted to bind to a port number number 1024 would return a nonsensical error message; a clear error explaining that privileged ports cannot be bound is now returned.
- Fixed a bug where the `podman quadlet list` and `podman quadlet rm` commands did not function properly with uninstantiated template Quadlets.
- Fixed a bug where the `podman quadlet install` command would occasionally fail to install a Quadlet if non-quadlet files were specified.
- Fixed a bug where the `podman quadlet install` command would not refuse to install Quadlets including non-quadlet files if the `--application` option was not specified.
- Fixed a bug where healthcheck logs could be corrupted, preventing proper healthcheck operation, if a healthcheck was killed midway through writing the file.
- Fixed a bug where the `podman volume prune --all` command incorrectly discarded label filters, causing `podman volume prune --all --filter label=foo` to prune all volumes, not just those with the `foo` label.
- Fixed a bug where the `podman events --format=json` command would print `null` instead of an error when the server sent an event that could not be decoded.
- Fixed a bug where a race condition could cause Quadlet to generate corrupt systemd units ([#2

_[Truncated at 4000 characters — full notes: https://github.com/podman-container-tools/podman/releases/tag/v6.1.0-rc1]_

### v6.0.2

- Date: 2026-07-22
- Version: v6.0.2
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v6.0.2
- Permalink: https://whatsnew.fyi/product/podman/releases/v6.0.2

- **fixed** — Fixed a bug where podman machine VMs created by the WSL provider on Windows were not properly cleaned up if the podman machine init command failed
- **fixed** — Fixed a bug where the Windows installer for Podman would, when installing for all users, incorrectly modify the path of only the user installing Podman
- **fixed** — Fixed a bug where the remote Podman client would throw errors when run on a Linux system that was not using Cgroups v2
- **changed** — Updated Buildah to v1.44.1

###### Bugfixes
- Fixed a bug where `podman machine` VMs created by the WSL provider on Windows were not properly cleaned up if the `podman machine init` command failed ([#27036](https://github.com/podman-container-tools/podman/issues/27036)).
- Fixed a bug where the Windows installer for Podman would, when installing for all users, incorrectly modify the path of only the user installing Podman ([#29160](https://github.com/podman-container-tools/podman/issues/29160)).
- Fixed a bug where the remote Podman client would throw errors when run on a Linux system that was not using Cgroups v2 ([#29241](https://github.com/podman-container-tools/podman/issues/29241)).

###### Misc
- Updated Buildah to v1.44.1

### v6.0.1

- Date: 2026-07-08
- Version: v6.0.1
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v6.0.1
- Permalink: https://whatsnew.fyi/product/podman/releases/v6.0.1

- **fixed** — Podman Machine VMs on Mac using the libkrun provider could be regularly turned off by a port-scanning process on the host unintentionally commanding the VM to shut down
- **fixed** — The podman machine init command would fail on Windows hosts when using the hyperv provider when WSL was not installed
- **fixed** — The podman machine init command would fail on Windows hosts when using the wsl provider when the user was a Hyper-V admin but Hyper-V is disabled
- **fixed** — Error messages from the OCI runtime were sometimes not displayed when --log-level=debug was passed to Podman
- **fixed** — The podman machine os upgrade command did not function properly
- **fixed** — The default image used by podman machine was not being properly cached
- **fixed** — Rootful Podman Machine VMs on Windows using the wsl provider would fail to start
- **fixed** — Commands that did not support the --replace option would incorrectly suggest using that option in error messages
- **fixed** — The Pesto rootless port forwarding tool enabled by rootless_port_forwarder=pasta did not properly clean up rules on container restart and network reload, causing failures to forward traffic

###### Bugfixes
- Fixed a bug where Podman Machine VMs on Mac using the `libkrun` provider could be regularly turned off by a port-scanning process on the host unintentionally commanding the VM to shut down.
- Fixed a bug where the `podman machine init` command would fail on Windows hosts when using the `hyperv` provider when WSL was not installed ([#29053](https://github.com/podman-container-tools/podman/issues/29053)).
- Fixed a bug where the `podman machine init` command would fail on Windows hosts when using the `wsl` provider when the user was a Hyper-V admin but Hyper-V is disabled ([#29138](https://github.com/podman-container-tools/podman/issues/29138)).
- Fixed a bug where error messages from the OCI runtime were sometimes not displayed when `--log-level=debug` was passed to Podman.
- Fixed a bug where the `podman machine os upgrade` command did not function properly ([#29085](https://github.com/podman-container-tools/podman/issues/29085)).
- Fixed a bug where the default image used by `podman machine` was not being properly cached ([#29090](https://github.com/podman-container-tools/podman/issues/29090)).
- Fixed a bug where rootful Podman Machine VMs on Windows using the `wsl` provider would fail to start ([#29003](https://github.com/podman-container-tools/podman/issues/29003)).
- Fixed a bug where commands that did not support the `--replace` option would incorrectly suggest using that option in error messages ([#24537](https://github.com/podman-container-tools/podman/issues/24537)).
- Fixed a bug where the Pesto rootless port forwarding tool (enabled by `rootless_port_forwarder=pasta`) did not properly clean up rules on container restart and network reload, causing failures to forward traffic ([#29032](https://github.com/podman-container-tools/podman/issues/29032)).

### v5.8.5

- Date: 2026-07-08
- Version: v5.8.5
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v5.8.5
- Permalink: https://whatsnew.fyi/product/podman/releases/v5.8.5

- **fixed** — Fixed a bug where Podman Machine VMs on Mac using the libkrun provider could be regularly turned off by a port-scanning process on the host unintentionally commanding the VM to shut down

###### Bugfixes
- Fixed a bug where Podman Machine VMs on Mac using the libkrun provider could be regularly turned off by a port-scanning process on the host unintentionally commanding the VM to shut down.

### v5.8.4

- Date: 2026-06-26
- Version: v5.8.4
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v5.8.4
- Permalink: https://whatsnew.fyi/product/podman/releases/v5.8.4

- **security** — Address CVE-2026-57231 where malicious image Env entries could leak host environment variables into containers
- **security** — Update golang.org/x/crypto library to v0.53.0 addressing CVE-2026-39830 and CVE-2026-42508
- **fixed** — Fix remote Podman client podman save command failure on Linux when using -f oci-dir or -f docker-dir arguments

###### Security
- This release addresses CVE-2026-57231, where a malicious image using malformed `Env` entries could cause host environment variables to leak into containers run based on the image, including the ability to use the `*` glob operator to leak large numbers of environment variables without knowing their exact names ([GHSA-4hq8-gpf5-8p68](https://github.com/podman-container-tools/podman/security/advisories/GHSA-4hq8-gpf5-8p68)).
- The golang.org/x/crypto library has been updated to v0.53.0, addressing CVE-2026-39830 and CVE-2026-42508.

###### Bugfixes
- Fixed a bug where the remote Podman client's `podman save` command would fail on Linux when using the `-f oci-dir` or `-f docker-dir` arguments.

### v6.0.0

- Date: 2026-06-24
- Version: v6.0.0
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v6.0.0
- Permalink: https://whatsnew.fyi/product/podman/releases/v6.0.0

- **security** — Address CVE-2026-57231 where a malicious image using malformed Env entries could cause host environment variables to leak into containers, including the ability to use the * glob operator to leak large numbers of environment variables
- **removed** — Support for BoltDB databases has been dropped in favor of automatic migration to SQLite
- **removed** — Support for running on Intel Macs has been removed
- **removed** — Support for running on Windows 10 has been removed
- **removed** — Support for running on cgroups v1 systems has been removed
- **removed** — Support for running on iptables has been removed in favor of nftables
- **removed** — Support for CNI networking has been removed in favor of Netavark
- **removed** — Support for the slirp4netns rootless network stack has been removed in favor of Pasta
- **removed** — The --network-cmd-path global option has been removed
- **changed** — Podman's configuration file parsing logic has been rewritten
- **changed** — Podman's import path has changed from github.com/containers/podman/v5 to go.podman.io/podman/v6
- **changed** — Network isolation now defaults to enabled for improved Docker compatibility and security
- **changed** — The way the podman quadlet suite of commands functions has been changed to use subdirectories instead of .app files
- **changed** — VMs made by podman machine on Linux now mount volumes from the host using systemd
- **changed** — The podman volume prune command now matches Docker's behavior by only pruning unused anonymous volumes
- **changed** — The podman volume list command now combines multiple filters using logical AND instead of logical OR
- **changed** — The label!= filter now combines multiple instances using logical AND instead of logical OR
- **changed** — The --format='{{json .Labels}}' option to podman ps, podman pod ps, and podman volume ls now prints output as comma-separated key=value pairs instead of as a JSON map
- **removed** — The --all-providers option to podman machine list has been removed
- **changed** — The MemorySwappiness field of podman inspect is now set to nil when not explicitly set by the user
- **changed** — The podman commit command now pauses the container while committing changes for improved security
- **removed** — The redundant nameOrID parameter has been removed from the artifacts.Remove() function in the Go bindings for the REST API
- **changed** — The minimum Go version required to build Podman is now v1.25

###### Security
- This release addresses CVE-2026-57231, where a malicious image using malformed `Env` entries could cause host environment variables to leak into containers run based on the image, including the ability to use the `*` glob operator to leak large numbers of environment variables without knowing their exact names ([GHSA-4hq8-gpf5-8p68](https://github.com/podman-container-tools/podman/security/advisories/GHSA-4hq8-gpf5-8p68)).

###### Breaking Changes
- Due to breaking changes in this release, Podman v6.0.0 must be used with Buildah v1.44.0, Skopeo v1.23, Netavark and Aardvark v2.0.0, and configuration files from the container-libs repository's common/v0.68.0 release.
- Support for BoltDB databases has been dropped. Starting Podman 6 when the BoltDB database is in use will have Podman attempt an automatic migration from BoltDB to SQLite.
- Support for running on Intel Macs has been removed.
- Support for running on Windows 10 has been removed.
- Support for running on cgroups v1 systems has been removed. Please update your system to use cgroups v2.
- Support for running on iptables has been removed. Please use nftables instead.
- Support for CNI networking has been removed. Please use Netavark instead.
- Support for the slirp4netns rootless network stack has been removed. Please use Pasta instead. As part of this, the `--network-cmd-path` global option, only used with `slirp4netns`, has been removed.
- Podman's configuration file parsing logic has seen a major rewrite. Please see [this document](https://github.com/podman-container-tools/podman/blob/main/contrib/design-docs/config-file-parsing.md) for exact details.
- Podman's import path has changed from `github.com/containers/podman/v5` to `go.podman.io/podman/v6` as part of our move into a CNCF-owned GitHub organization.
- Network isolation now defaults to enabled, improving Docker compatibility and security. A special workaround for the Docker-compatible API related to isolation being disabled has been removed ([#27349](https://github.com/podman-container-tools/podman/issues/27349)).
- The way the `podman quadlet` suite of commands functions has been changed. Previously, Quadlets and their associated files were tracked using a `.app` file, ensuring that removing a Quadlet also removed all associated non-Quadlet files. Now, Quadlets and associated files are placed in subdirectories, which should reduce bugs and make manual management of Quadlets added by `podman quadlet install` much easier.
- VMs made by `podman machine` on Linux now mount volumes from the host using systemd. Volume mounts on existing `podman machine` VMs on Linux have been broken by this change, and the VM will need to be recreated.
- The `podman volume prune` command now matches Docker's behavior by only pruning unused anonymous volumes. Please use the newly-added `--all` option for the previous behavior (pruning all volumes).
- The `podman volume list` command now combines multiple filters using logical `AND` instead of logical `OR` (meaning all filters must match for a container to be included in output) ([#26786](https://github.com/podman-container-tools/podman/issues/26786)).
- The `label!=` filter used in many commands now combines the output of multiple instances of the filter with logical `AND` instead of logical `OR`.
- The `--format='{{json .Labels}}` option to the `podman ps`, `podman pod ps`, and `podman volume ls` commands now prints its output as comma-separated `key=value` pairs instead of as a JSON map, improving Docker compatibility ([#21847](https://github.com/podman-container-tools/podman/issues/21847)).
- The `--all-providers` option to `podman machine list` has been removed, as machines from all providers can now be accessed by all commands.
- The `MemorySwappiness` field of `podman inspect` is now set to `nil` when not explicitly set by the user (instead of `-1`), improving Docker compatibility ([#23824](https://github.com/podman-container-tools/podman/issues/23824)).
-

_[Truncated at 4000 characters — full notes: https://github.com/podman-container-tools/podman/releases/tag/v6.0.0]_

### v6.0.0-rc1 — v6.0.0-RC1

- Date: 2026-06-12
- Version: v6.0.0-rc1
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v6.0.0-rc1
- Permalink: https://whatsnew.fyi/product/podman/releases/v6.0.0-rc1
- Labels: Pre-release

- **removed** — Support for BoltDB databases has been dropped
- **removed** — Support for running on Intel Macs has been removed
- **removed** — Support for running on Windows 10 has been removed
- **removed** — Support for running on cgroups v1 systems has been removed
- **removed** — Support for running on iptables has been removed
- **removed** — Support for CNI networking has been removed
- **removed** — Support for the slirp4netns rootless network stack has been removed
- **removed** — The --network-cmd-path global option has been removed
- **changed** — Podman's configuration file parsing logic has been rewritten
- **changed** — Podman's import path has changed from github.com/containers/podman/v5 to go.podman.io/podman/v6
- **changed** — Network isolation now defaults to enabled
- **changed** — The way the podman quadlet suite of commands functions has been changed to use subdirectories instead of .app files
- **changed** — VMs made by podman machine on Linux now mount volumes from the host using systemd
- **changed** — The podman volume prune command now only prunes unused anonymous volumes by default
- **changed** — The podman volume list command now combines multiple filters using logical AND instead of logical OR
- **changed** — The label!= filter now combines the output of multiple instances with logical AND instead of logical OR
- **changed** — The --format='{{json .Labels}}' option to podman ps, podman pod ps, and podman volume ls now prints output as comma-separated key=value pairs instead of a JSON map
- **removed** — The --all-providers option to podman machine list has been removed
- **changed** — The MemorySwappiness field of podman inspect is now set to nil when not explicitly set by the user
- **changed** — The podman commit command now pauses the container while committing changes
- **removed** — The Go bindings for the REST API have removed the redundant nameOrID parameter from the artifacts.Remove() function
- **changed** — The minimum Go version required to build Podman is now v1.25
- **added** — All podman machine commands can now operate on VMs from all providers regardless of the current provider setting
- **added** — A new command podman machine os update has been added to update the operating system of a podman machine VM
- **added** — A new command podman system hyperv-prep has been added to allow Windows administrators to prepare a host for running podman machine VMs
- **added** — When starting a VM with podman machine start or podman machine init --now, users will be prompted whether they want to change the default connection

###### Breaking Changes
- Due to breaking changes in this release, Podman v6.0.0 must be used with Buildah v1.44.0, Skopeo v1.23, Netavark and Aardvark v2.0.0, and configuration files from the container-libs repository's common/v0.68.0 release.
- Support for BoltDB databases has been dropped. Starting Podman 6 when the BoltDB database is in use will have Podman attempt an automatic migration from SQLite to BoltDB.
- Support for running on Intel Macs has been removed.
- Support for running on Windows 10 has been removed.
- Support for running on cgroups v1 systems has been removed. Please update your system to use cgroups v2.
- Support for running on iptables has been removed. Please use nftables instead.
- Support for CNI networking has been removed. Please use Netavark instead.
- Support for the slirp4netns rootless network stack has been removed. Please use Pasta instead. As part of this, the `--network-cmd-path` global option, only used with `slirp4netns`, has been removed.
- Podman's configuration file parsing logic has seen a major rewrite. Please see [this document](https://github.com/podman-container-tools/podman/blob/main/contrib/design-docs/config-file-parsing.md) for exact details.
- Podman's import path has changed from `github.com/containers/podman/v5` to `go.podman.io/podman/v6` as part of our move into a CNCF-owned GitHub organization.
- Network isolation now defaults to enabled, improving Docker compatibility and security. A special workaround for the Docker-compatible API related to isolation being disabled has been removed ([#27349](https://github.com/podman-container-tools/podman/issues/27349)).
- The way the `podman quadlet` suite of commands functions has been changed. Previously, Quadlets and their associated files were tracked using a `.app` file, ensuring that removing a Quadlet also removed all associated non-Quadlet files. Now, Quadlets and associated files are placed in subdirectories, which should reduce bugs and make manual management of Quadlets added by `podman quadlet install` much easier.
- VMs made by `podman machine` on Linux now mount volumes from the host using systemd. Volume mounts on existing `podman machine` VMs on Linux have been broken by this change, and the VM will need to be recreated.
- The `podman volume prune` command now matches Docker's behavior by only pruning unused anonymous volumes. Please use the newly-added `--all` option for the previous behavior (pruning all volumes).
- The `podman volume list` command now combines multiple filters using logical `AND` instead of logical `OR` (meaning all filters must match for a container to be included in output) ([#26786](https://github.com/podman-container-tools/podman/issues/26786)).
- The `label!=` filter used in many commands now combines the output of multiple instances of the filter with logical `AND` instead of logical `OR`.
- The `--format='{{json .Labels}}` option to the `podman ps`, `podman pod ps`, and `podman volume ls` commands now prints its output as comma-separated `key=value` pairs instead of as a JSON map, improving Docker compatibility ([#21847](https://github.com/podman-container-tools/podman/issues/21847)).
- The `--all-providers` option to `podman machine list` has been removed, as machines from all providers can now be accessed by all commands.
- The `MemorySwappiness` field of `podman inspect` is now set to `nil` when not explicitly set by the user (instead of `-1`), improving Docker compatibility ([#23824](https://github.com/podman-container-tools/podman/issues/23824)).
- The `podman commit` command now pauses the container while committing changes, improving security by restricting concurrent modification. The prior behavior can be restored by using `podman commit --pause=false ...`.
- The Go bindings for the REST API have removed the redundant `nameOrID` parameter from the `artifacts.Remove()` function.
- The minimum Go version required to build Podman is now v1.25.

###### Features
- All `podman machine` co

_[Truncated at 4000 characters — full notes: https://github.com/podman-container-tools/podman/releases/tag/v6.0.0-rc1]_

### v5.8.3

- Date: 2026-06-12
- Version: v5.8.3
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v5.8.3
- Permalink: https://whatsnew.fyi/product/podman/releases/v5.8.3

- **security** — Fix CVE-2026-44517 where building a Dockerfile using ADD or COPY instructions accessing a malicious Git repository or tar archive could cause files outside the build context directory to be included in the build context or copied into the build
- **changed** — Update Buildah to v1.43.2
- **changed** — Update gvisor-tap-vsock to v0.8.9

###### Security
- This release addresses CVE-2026-44517, where building a Dockerfile using a `ADD` or `COPY` instruction accessing a malicious Git repository or tar archive could cause files outside the build context directory to be included in the build context or copied into the build. Please see [GHSA-49p4-px3h-rq49](https://github.com/podman-container-tools/buildah/security/advisories/GHSA-49p4-px3h-rq49) for more details.

###### Misc
- Updated Buildah to v1.43.2
- Updated gvisor-tap-vsock to v0.8.9

### v5.8.2

- Date: 2026-04-14
- Version: v5.8.2
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v5.8.2
- Permalink: https://whatsnew.fyi/product/podman/releases/v5.8.2

- **security** — Address CVE-2026-33414 where podman machine init --image command on Windows using the Hyper-V backend could run PowerShell-escaped commands from the user-specified image path in a PowerShell session on the host
- **fixed** — Fix containers with the unless-stopped restart policy not restarting after a reboot when podman-restart.service is enabled
- **fixed** — Fix setting Entrypoint="" in a Quadlet .container file not clearing the container's entrypoint
- **fixed** — Fix setting a HealthCmd in a Quadlet .container file to a command that includes double-quotes resulting in a nonfunctional healthcheck due to a parsing issue
- **fixed** — Fix FreeBSD systems panicking when inspecting containers created with the host network mode
- **fixed** — Fix the Libpod System Check endpoint performing operations with bad data after returning a 400 error
- **fixed** — Fix the remote attach API for containers (Libpod & Compat) panicking due to a rare race condition
- **fixed** — Fix the Secret Create API not creating functional secrets using the shell driver due to options from the default driver being improperly added
- **changed** — Update Buildah to v1.43.1
- **changed** — Update containers/common library to v0.67.1
- **changed** — Update containers/image library to v5.39.2

###### Security
- This release addresses CVE-2026-33414, where the `podman machine init --image` command when run on Windows using the Hyper-V backend can run PowerShell-escaped commands from the user-specified image path on in a PowerShell session on the host ([GHSA-hc8w-h2mf-hp59](https://github.com/containers/podman/security/advisories/GHSA-hc8w-h2mf-hp59)).

###### Bugfixes
- Fixed a bug where containers with the `unless-stopped` restart policy would not restart after a reboot when `podman-restart.service` was enabled ([#28152](https://github.com/containers/podman/issues/28152)).
- Fixed a bug where setting `Entrypoint=""` in a Quadlet `.container` file did not clear the container's entrypoint ([#28213](https://github.com/containers/podman/issues/28213)).
- Fixed a bug where setting a `HealthCmd` in a Quadlet `.container` file to a command that included double-quotes (`"`) would result in a nonfunctional healthcheck due to a parsing issue ([#28409](https://github.com/containers/podman/issues/28409)).
- Fixed a bug where FreeBSD systems could panic when inspecting containers created with the `host` network mode ([#28289](https://github.com/containers/podman/issues/28289)).

###### API
- Fixed a bug where the Libpod System Check endpoint could perform operations with bad data after returning a 400 error ([#28350](https://github.com/containers/podman/issues/28350)).
- Fixed a bug where the remote attach API for containers (Libpod & Compat) could panic due to a rare race condition ([#28277](https://github.com/containers/podman/issues/28277)).
- Fixed a bug where the Secret Create API could not create functional secrets using the `shell` driver due to options from the default driver being improperly added.

###### Misc
- Updated Buildah to v1.43.1
- Updated the containers/common library to v0.67.1
- Updated the containers/image library to v5.39.2

### v5.8.1

- Date: 2026-03-11
- Version: v5.8.1
- Original notes: https://github.com/podman-container-tools/podman/releases/tag/v5.8.1
- Permalink: https://whatsnew.fyi/product/podman/releases/v5.8.1

- **fixed** — Fixed a critical bug where automatic migration from BoltDB to SQLite after a reboot could perform a partial migration with some containers in SQLite and some remaining in BoltDB when Quadlets were in use

###### Bugfixes
- Fixed a critical bug where automatic migration from BoltDB to SQLite after a reboot could perform a partial migration, with some containers in SQLite and some remaining in BoltDB, when Quadlets were in use ([#28215](https://github.com/containers/podman/issues/28216)). For those who encountered this bug with 5.8.0 there is no way to automatically recover. If you do not have persistent containers/pods/volumes (i.e. all containers are run using Quadlets) then the easiest option is to move the `db.sql` file in Podman's storage directory to `db.sql.bak` (or similar) and reboot again with v5.8.1 to attempt another migration. Please contact the maintainers with any issues during migration and we will assist as able.