August 2026 - Podman - Podman List Archives

Podman v5.8.6 Released
by container.tools.ci＠gmail.com 13 Aug '26

13 Aug '26

Hi all, Podman v5.8.6 is now available. You may view the full details at https://github.com/podman-container-tools/podman/releases/tag/v5.8.6 Release Notes: -------------- ### Security - This release addressed [CVE-2026-19730](https://github.com/podman-container-tools/podman/security/a… where the `podman quadlet install --replace` command did not truncate the file being replaced, meaning replacing a longer file with a shorter one would result in content from the original file incorrectly being retained.

1 0

Podman v6.1.0 Released
by container.tools.ci＠gmail.com 12 Aug '26

12 Aug '26

Hi all, Podman v6.1.0 is now available. You may view the full details at https://github.com/podman-container-tools/podman/releases/tag/v6.1.0 Release Notes: -------------- ### 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)). - A new option, `force_port_listen`, has been added to `containers.conf`. This is required to be set when running Podman on WSL to support port forwarding from the Windows host. It is automatically set on newly-created `podman machine` VMs on Windows using the WSL provider. ### 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 ([#29004](https://github.com/podman-container-tools/podman/issues/29004)). - Fixed a bug where the `podman inspect` command on a container with a single-element command (e.g. `podman run fedora bash`) would include the command in both `Path` and `Args`, when it should only have been included in `Path` ([#29155](https://github.com/podman-container-tools/podman/issues/29155)). - Fixed a bug where the `--format` option to `podman inspect` on containers did not properly support some format specifiers supported by Docker (e.g. `{{.HostIp}}` did not work, but `{{.HostIP}}` did) ([#29164](https://github.com/podman-container-tools/podman/issues/29164)). - Fixed a bug where the Quadlet generator would not write error messages to `STDERR` but only to `/dev/kmsg`, meaning that errors were not visible from `systemd-analyze --generators verify` and other tooling invoking the systemd generator directly. - Fixed a bug where containers which failed to start would, in some circumstances, not properly clean up, resulting in improper behavior ([#26143](https://github.com/podman-container-tools/podman/issues/26143)). - Fixed a bug where the `podman kube generate` command would improperly generate warning messages only applicable when running as a rootless user on an SELinux enabled system when not running in that configuration ([#17743](https://github.com/podman-container-tools/podman/issues/17743)). ### API - Fixed a bug where the Compat and Libpod Create endpoint for Exec Sessions (`/containers/$CID/exec`) did not honor the `ConsoleSize` parameter in the exec config. - The Compat API has seen further changes to improve support for the Docker v1.44 API, including the deprecation of several fields removed in that release. - Preparations have begun to implement support for the v1.45 API. ### Misc - Updated Buildah to v1.45.0 - Updated the image library to v5.41.1 - Updated the storage library to v1.64.0 - Updated the common library to v0.69.1

1 0

Confirm expected Apple installer signer for official Podman v6.0.2 macOS package
by Rafael Burgos 05 Aug '26

05 Aug '26

Hello, I'm trying to independently confirm the expected code-signing identity for the official Podman v6.0.2 macOS installer before using it, and I couldn't find this documented anywhere outside the package itself. The asset in question is: podman-installer-macos-arm64.pkg, from the official v6.0.2 GitHub release, at: https://github.com/podman-container-tools/podman/releases/download/v6.0.2/p… - Byte size: 74802386 - SHA-256: 5a1d97f98f626cdb82dbd9932cf43102d1e9b6621627085fec2dcadf59743930 I downloaded this exact asset and it passed byte-size verification, SHA-256 verification, Apple code-signature validation, and notarization assessment. The observed signer is: Developer ID Installer: Red Hat, Inc. (HYSCB8KRL2) I'd like to ask: 1. Is this exact Developer ID Installer identity and Team ID (HYSCB8KRL2) the expected signer for official Podman macOS installers? 2. Is there a maintained, authoritative project or publisher page that documents this expected signing identity, that I could reference going forward? 3. Should the same signer identity be expected for future official Podman macOS installer releases, or does this rotate? Thanks for any pointer you can give me.

1 0

How to load multiple podman images at system boot?
by HUANG, TONY 04 Aug '26

04 Aug '26

Hi, I have a bunch of podman containers that I would like to load at system boot. I am running RHEL 8.10. I have something like this for startup: [Unit] Description=Load Podman images at system boot After=network.target [Service] Type=oneshot User=test ExecStart=/usr/bin/podman load --input /path/to/image_directory RemainAfterExit=yes [Install] WantedBy=multi-user.target But systemd keeps on exiting at exit-code 125; nonetheless, if I load it manually, the container will load even seeing the chatty messages. Furthermore, how can I redirect /var/tmp to somewhere else? can I identify that environment variable in systemd? thanks! --T

1 0