- Podman - Podman List Archives

help setting up my rootless container
by Felix Rubio 10 Dec '25

10 Dec '25

Hi everybody, I hope somebody can give me a hand, as I have looked around for many hours unsuccessfully already. I am setting up a number of rootless containers, each one run by its ad-hoc user, and some of those need to communicate between them. To do this, I am publishing their ports on a veth (10.255.255.1) and... I cannot get them to see each other. I have also tried with the --network=host parameter (assuming I would loose the network sandboxing then), to no luck. I am using podman 5.4 on debian trixie, in case that matters. Anybody has any idea on what might be wrong? Thank you for any help you can provide! -- Felix

1 0

Podman v5.7.1 Released
by container.tools.ci＠gmail.com 10 Dec '25

10 Dec '25

Hi all, Podman v5.7.1 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.7.1 Release Notes: -------------- ### Bugfixes - Fixed a bug where adding devices to emulated Linux containers on FreeBSD did not work. - Fixed a bug where the `podman system migrate` command could panic under certain circumstances when run rootless. - Fixed a bug where Podman would sometimes not correctly recreate the rootless user namespace when Conmon and the rootless pause process were unexpectedly killed. - Fixed a bug where the `podman kube play` command could leak file descriptors. ### Misc - Updated Buildah to v1.42.2 - Updated containers/common to v0.66.1

1 0

Re: [Podman-desktop]Podman Desktop fails to detect WSL2 even though installed – Need vendor guidance
by Jeff Maury 08 Dec '25

08 Dec '25

Sekar, If you provide an installation package, so I would recommend that you install Podman in addition to Podman Desktop and that once both are installed, you create a Podman machine so that users have everything setup. Podman installers are available at github.com/containers/podman HTH Jeff On Mon, Dec 8, 2025 at 8:03 AM Sekar Sivaguru <sivaguru.sekar(a)hm.com> wrote: > Hi Maury, > > We are currently working on creating a deployment package for Podman > Desktop that can be installed across multiple machines. Our goal is to > include the Podman engine within this package so that users do not need to > perform manual setup steps after installation. > > When we deploy the package on other machines, we encounter initialization > errors (as shown in the attached screenshot). These errors seem related to > missing configurations that are normally handled manually according to the > official documentation. > > Could you please advise on the recommended approach to: > > > - Bundle Podman engine with Podman Desktop in a single package > > > > - Ensure that all necessary configurations are applied automatically > during installation > > > > - Avoid requiring users to follow manual steps from the installation > guide > > > Our aim is to fully automate the setup process for a seamless user > experience. Please refer to the documentation for any specific steps we > should incorporate. Thank you for your guidance. > > Best regards, > Sekar Sivaguru > ------------------------------ > *From:* Jean-Francois Maury <jmaury(a)redhat.com> > *Sent:* Monday, December 8, 2025 11:44 AM > *To:* Sekar Sivaguru <sivaguru.sekar(a)hm.com>; > podman-desktop(a)lists.podman.io <podman-desktop(a)lists.podman.io>; > podman(a)lists.podman.io <podman(a)lists.podman.io> > *Subject:* Re: [Podman-desktop]Podman Desktop fails to detect WSL2 even > though installed – Need vendor guidance > > Can you provide more details on the scenario? When does it happen? What's > the error message? > > Thanks > Jeff > > Le 5 décembre 2025 20:54:14 Sekar Sivaguru via Podman-desktop < > podman-desktop(a)lists.podman.io> a écrit : > > Dear Team > Podman Desktop fails to detect WSL2 even though wsl --version confirms > WSL2 is installed. Is this a known issue? What is the official fix or > configuration required to ensure Podman Desktop consistently detects WSL2 > across multiple devices when installing Podman?” > Request for Clarification: > > - Why does Podman Desktop fail to detect WSL2 in this scenario? > - Is this a known issue or configuration requirement? > - What is the official fix or recommended steps to ensure Podman > Desktop consistently detects WSL2 across multiple devices? > > Thank you for your support. > Best regards, > Sivaguru Sekar > > > THE INFORMATION CONTAINED IN THIS EMAIL MESSAGE MAY BE PRIVILEGED, > CONFIDENTIAL, AND PROTECTED FROM DISCLOSURE ANY UNAUTHORIZED USE, PRINTING, > COPYING, DISCLOSURE OR DISSEMINATION OF THIS COMMUNICATION MAY BE SUBJECT > TO LEGAL RESTRICTION OR SANCTION IF YOU THINK THAT YOU HAVE RECEIVED THIS > E-MAIL MESSAGE IN ERROR, PLEASE REPLY TO THE SENDER AND DELETE THIS MESSAGE > FROM YOUR COMPUTER. > _______________________________________________ > Podman-desktop mailing list -- podman-desktop(a)lists.podman.io > To unsubscribe send an email to podman-desktop-leave(a)lists.podman.io > > > > Envoyé avec Aqua Mail pour Android > <https://link-aquamail.dynalinks.app/dl/signature> > -- Jeff Maury Podman Desktop team Engineering Manager, DevTools Red Hat EMEA <https://www.redhat.com> jmaury(a)redhat.com @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com> <https://redhat.com/summit>

1 0

Re: [Podman-desktop]Podman Desktop fails to detect WSL2 even though installed – Need vendor guidance
by Jean-Francois Maury 08 Dec '25

08 Dec '25

Can you provide more details on the scenario? When does it happen? What's the error message? Thanks Jeff Le 5 décembre 2025 20:54:14 Sekar Sivaguru via Podman-desktop <podman-desktop(a)lists.podman.io> a écrit : > Dear Team > Podman Desktop fails to detect WSL2 even though wsl --version confirms WSL2 > is installed. Is this a known issue? What is the official fix or > configuration required to ensure Podman Desktop consistently detects WSL2 > across multiple devices when installing Podman?” > Request for Clarification: > Why does Podman Desktop fail to detect WSL2 in this scenario? > Is this a known issue or configuration requirement? > What is the official fix or recommended steps to ensure Podman Desktop > consistently detects WSL2 across multiple devices? > Thank you for your support. > Best regards, > Sivaguru Sekar > > > THE INFORMATION CONTAINED IN THIS EMAIL MESSAGE MAY BE PRIVILEGED, > CONFIDENTIAL, AND PROTECTED FROM DISCLOSURE ANY UNAUTHORIZED USE, PRINTING, > COPYING, DISCLOSURE OR DISSEMINATION OF THIS COMMUNICATION MAY BE SUBJECT > TO LEGAL RESTRICTION OR SANCTION IF YOU THINK THAT YOU HAVE RECEIVED THIS > E-MAIL MESSAGE IN ERROR, PLEASE REPLY TO THE SENDER AND DELETE THIS MESSAGE > FROM YOUR COMPUTER. > _______________________________________________ > Podman-desktop mailing list -- podman-desktop(a)lists.podman.io > To unsubscribe send an email to podman-desktop-leave(a)lists.podman.io Envoyé avec Aqua Mail pour Android

2 1

Re: [Podman-desktop]Podman Desktop fails to detect WSL2 even though installed – Need vendor guidance
by Jeff Maury 06 Dec '25

06 Dec '25

Hello, can you tell us more about the scenario ? When do you get an error message? On Fri, Dec 5, 2025 at 8:54 PM Sekar Sivaguru via Podman-desktop < podman-desktop(a)lists.podman.io> wrote: > Dear Team > Podman Desktop fails to detect WSL2 even though wsl --version confirms > WSL2 is installed. Is this a known issue? What is the official fix or > configuration required to ensure Podman Desktop consistently detects WSL2 > across multiple devices when installing Podman?” > Request for Clarification: > > - Why does Podman Desktop fail to detect WSL2 in this scenario? > - Is this a known issue or configuration requirement? > - What is the official fix or recommended steps to ensure Podman > Desktop consistently detects WSL2 across multiple devices? > > Thank you for your support. > Best regards, > Sivaguru Sekar > > > THE INFORMATION CONTAINED IN THIS EMAIL MESSAGE MAY BE PRIVILEGED, > CONFIDENTIAL, AND PROTECTED FROM DISCLOSURE ANY UNAUTHORIZED USE, PRINTING, > COPYING, DISCLOSURE OR DISSEMINATION OF THIS COMMUNICATION MAY BE SUBJECT > TO LEGAL RESTRICTION OR SANCTION IF YOU THINK THAT YOU HAVE RECEIVED THIS > E-MAIL MESSAGE IN ERROR, PLEASE REPLY TO THE SENDER AND DELETE THIS MESSAGE > FROM YOUR COMPUTER. > _______________________________________________ > Podman-desktop mailing list -- podman-desktop(a)lists.podman.io > To unsubscribe send an email to podman-desktop-leave(a)lists.podman.io > -- Jeff Maury Podman Desktop team Engineering Manager, DevTools Red Hat EMEA <https://www.redhat.com> jmaury(a)redhat.com @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com> <https://redhat.com/summit>

1 0

Podman Community Meeting - Tues, Dec 2, 2025, 11:00 am EST (UTC-5)
by Tom Sweeney 01 Dec '25

01 Dec '25

With all the holiday goings on, don't forget the Podman Community meeting tomorrow, Tuesday, December 2, 2025, at 11:00 am EST (UTC-5)! We'll have a 2025 retro, talk about immutable GitHub releases, Materia, and probably more! Video link in agenda, and room for another topic or two! Hope to see you there! t agenda: https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w

1 0

Podman v5.7.0 Released
by container.tools.ci＠gmail.com 11 Nov '25

11 Nov '25

Hi all, Podman v5.7.0 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.7.0 Release Notes: -------------- ### Security - This release addresses CVE-2025-52881, where arbitrary write gadgets and procfs write redirects allowed runc container escape and denial of service. ### Features - The remote Podman client and `podman system service` API server now support encrypting connections with TLS and mTLS, including client authentication by certificate ([#24583](https://github.com/containers/podman/issues/24583)). - The `podman system connection add` command can now create connections to TCP sockets with TLS and mTLS encryption. - The `podman run` and `podman create` commands now support two new options, `--creds` and `--cert-dir`, to manage logging into registries to pull images. - The `podman kube play` and `podman kube down` commands can now accept multiple files as input, creating or removing more than one pod or deployment with the same command ([#26274](github.com/containers/podman/issues/26274)). - The `podman kube play` command now supports a new option, `--no-pod-prefix`, to disable prefixing container names with pod names. Please note that this can cause pods to fail to create if the pod shares a name with a container ([#26396](https://github.com/containers/podman/issues/26396)). - The `podman machine init` command now supports a new option, `--tls-verify`, to control whether the machine image can be pulled from registries without a trusted TLS certificate, with the default being `true` (TLS verification on) ([#26517](https://github.com/containers/podman/issues/26517)). - When running the `podman image load` and `podman build` commands against a `podman machine` VM, if the path being loaded or built is shared into the VM, Podman will load it from the VM's filesystem instead of streaming the data through the REST API, improving performance ([#26321](https://github.com/containers/podman/issues/26321)). - A default location for container log files when using the `k8s-file` log driver can now be specified with the `log_path` option in `containers.conf`. - Default flags for the OCI runtime can now be set with the `runtimes_flags` option in `containers.conf`. - The `podman artifact remove` command can now accept multiple arguments, for example, `podman artifact rm artifact1 artifact2`. - The `podman wait` command now supports a new option, `--return-on-first`, which causes `podman wait` to return after *any* container matches the condition, as opposed to waiting for *all* containers to match ([#26691](https://github.com/containers/podman/issues/26691)). - The `podman container restore` command now supports a new option, `--tcp-close`, allowing containers with active TCP connections to be restored multiple times. - Quadlet now features support for a new file type, `.artifact`, allowing OCI artifacts to be managed with Quadlet ([#25778](https://github.com/containers/podman/issues/25778)). - Quadlet `.container` files now support a new key, `HttpProxy`, to disable the automatic forwarding of HTTP proxy options from the host into the container ([#26925](https://github.com/containers/podman/issues/26925)). - Quadlet `.pod` files now support a new key, `StopTimeout`, to configure the stop timeout for the pod ([#27120](https://github.com/containers/podman/issues/27120)). - Quadlet `.build` files now support two new keys, `BuildArg` and `IgnoreFile`, to specify build arguments and an ignore file ([#27065](https://github.com/containers/podman/issues/27065) and [#27268](https://github.com/containers/podman/issues/27268)). - Quadlet `.kube` files now support multiple YAML files in a single `.kube` file. - Quadlet now supports templated dependencies for volumes and networks ([#25136](https://github.com/containers/podman/issues/25136)). - The `podman quadlet install` command now supports a new option, `--replace`, which will replace any existing Quadlet with a conflicting name ([#26930](https://github.com/containers/podman/issues/26930)). - The `podman quadlet print` command now has a new alias, `podman quadlet cat` ([#27296](https://github.com/containers/podman/issues/27296)). - The remote Podman client's `podman artifact remove` command now supports the `--all` option. - The `podman artifact add` command now supports a new option, `--replace`, which will replace any existing artifact with the given name ([#27082](https://github.com/containers/podman/issues/27082)). - The `podman artifact rm` command now supports a new option, `--ignore`, which will suppress errors when attempting to remove an artifact that does not exist ([#27084](https://github.com/containers/podman/issues/27084)). - The `podman artifact list` command now includes artifact creation time in its output ([#27314](https://github.com/containers/podman/issues/27314)). - The `podman artifact list --format` option now supports two new format keys, `VirtualSize`, returning the size of the artifact in integer bytes, and `CreatedAt`, returning the time the artifact was created as an RFC3339 timestamp (the existing `Size` and `Created` fields returned human-readable information) ([#27085](https://github.com/containers/podman/issues/27085)). - The `podman artifact inspect` command now supports a new option, `--format`, to return specific information about an artifact with user-specified formatting ([#27112](https://github.com/containers/podman/issues/27112)). ### Changes - In preparation for a planned removal of the BoltDB database in Podman 6.0, a warning has been added for installations still using BoltDB. These warnings were added in Podman 5.6, but were not visible by default; they now are. They can be suppressed with the `SUPPRESS_BOLTDB_WARNING=true` environment variable. - A new Windows installer has been introduced with a simpler single MSI architecture that supports both user-scope (no admin required) and machine-scope installations. Note: To use the new installer, users must uninstall existing Podman installations before using the new installer, but all containers, images, machines, and other data will be preserved. The old installer is still provided to ensure backwards compatibility, though it will be removed in a future release ([#22994](https://github.com/containers/podman/issues/22994) and [#25968](https://github.com/containers/podman/issues/25968)). - Podman now requires Go 1.24. - When the `-p`/`--publish` and `--network=ns:/path` options are used together when creating a container, Podman will not warn that the `-p` option will be ignored as an existing namespace is in use (this has always been the case, but Podman now prints a warning about it) ([#26663](https://github.com/containers/podman/issues/26663)). - The `podman stats` command now provides additional information about container resource utilization when run on FreeBSD. - Shell autocompletion has been enabled for the `--sysctl` option to `podman create` and `podman run`, and the `--interface-name` option to `podman network create`. - Artifacts created by Podman now include a creation timestamp by default, stored in the `org.opencontainers.image.created` annotation ([#27081](https://github.com/containers/podman/issues/27081)). - The `podman inspect` command can now inspect artifacts. - The `podman artifact add` command can now override the `org.opencontainers.image.title` annotation in created artifacts. - Podman can now optionally be built with Sequoia-PGP support. When so built, the `--sign-by-sq-fingerprint` option allows signing images using Seqoia-PGP keys. ### Bugfixes - Fixed a bug where the `--filter ancestor=` option to `podman ps` required complete matches, unlike Docker (which matched substrings) ([#26623](https://github.com/containers/podman/issues/26623)). - Fixed a bug where the `--filter label=` option to `podman events` did not support key-only matches (as `podman os --filter label=` does) ([#26702](https://github.com/containers/podman/issues/26702)). - Fixed a bug where Quadlet could panic when a `Mount` was given without a `source` being specified. - Fixed a bug where Quadlet would fail to generate for a `.build` file when a systemd specifier was used in the `[Build]` section ([#26746](https://github.com/containers/podman/issues/26746)). - Fixed a bug where the `podman info` command could panic when `/proc/sys/fs/binfmt_misc` was not mounted. - Fixed a bug where the remote Podman client could lose some initial bytes of output from attach sessions (`podman run`, `podman exec`, `podman attach`) due to a race condition ([#26951](https://github.com/containers/podman/issues/26951)). - Fixed a bug where the `podman build` command was ignoring SBOM related options ([#23915](https://github.com/containers/podman/issues/23915)). - Fixed a bug where the `--userns=ns:/path` option to `podman create` and `podman run` was broken with runc 1.1.11 and higher ([#27148](https://github.com/containers/podman/issues/27148)). - Fixed a bug where `podman machine` on Windows would always re-pull machine images when using the WSL provider, even if an the image had already been pulled and was present on disk. ### API - Added a new API endpoint to list quadlets (`GET /libpod/quadlets/json`). - The Compat Inspect endpoint for Images no longer includes the `ContainerConfig` field. To access image configuration, use the `Config` field instead. This matches changes made by Docker in the v1.45 API. - Fixed a bug where the Stats and Commit endpoints for Containers (compat & libpod), the Push, Commit, Push, and Pull endpoints for Images (compat & libpod), and the Push endpoint for Manifests (libpod) were not returning a `Content-Type` header. ### Misc - Error messages returned when an incomplete `--device` option (for example `--device /dev/fuse::`) is passed to `podman create` or `podman run` have been improved. - Updated Buildah to v1.42.0 - Updated the containers/image library to v5.38.0 - Updated the containers/storage library to v1.61.0 - Updated the containers/common library to v0.66.0 - The containers/image, containers/storage, and containers/common libraries are now sourced from the [containers/container-libs](https://github.com/containers/container-libs/) monorepo.

1 0

Podman candidate v5.7.0-rc3 Released
by container.tools.ci＠gmail.com 05 Nov '25

05 Nov '25

Hi all, Podman candidate v5.7.0-rc3 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.7.0-rc3 Release candidate Notes: -------------- ### Features - The remote Podman client and `podman system service` API server now support encrypting connections with TLS and mTLS, including client authentication by certificate ([#24583](https://github.com/containers/podman/issues/24583)). - The `podman system connection add` command can now create connections to TCP sockets with TLS and mTLS encryption. - The `podman run` and `podman create` commands now support two new options, `--creds` and `--cert-dir`, to manage logging into registries to pull images. - The `podman kube play` and `podman kube down` commands can now accept multiple files as input, creating or removing more than one pod or deployment with the same command ([#26274](github.com/containers/podman/issues/26274)). - The `podman kube play` command now supports a new option, `--no-pod-prefix`, to disable prefixing container names with pod names. Please note that this can cause pods to fail to create if the pod shares a name with a container ([#26396](https://github.com/containers/podman/issues/26396)). - The `podman machine init` command now supports a new option, `--tls-verify`, to control whether the machine image can be pulled from registries without a trusted TLS certificate, with the default being `true` (TLS verification on) ([#26517](https://github.com/containers/podman/issues/26517)). - When running the `podman image load` and `podman build` commands against a `podman machine` VM, if the path being loaded or built is shared into the VM, Podman will load it from the VM's filesystem instead of streaming the data through the REST API, improving performance ([#26321](https://github.com/containers/podman/issues/26321)). - A default location for container log files when using the `k8s-file` log driver can now be specified with the `log_path` option in `containers.conf`. - Default flags for the OCI runtime can now be set with the `runtimes_flags` option in `containers.conf`. - The `podman artifact remove` command can now accept multiple arguments, for example, `podman artifact rm artifact1 artifact2`. - The `podman wait` command now supports a new option, `--return-on-first`, which causes `podman wait` to return after *any* container matches the condition, as opposed to waiting for *all* containers to match ([#26691](https://github.com/containers/podman/issues/26691)). - The `podman container restore` command now supports a new option, `--tcp-close`, allowing containers with active TCP connections to be restored multiple times. - Quadlet now features support for a new file type, `.artifact`, allowing OCI artifacts to be managed with Quadlet ([#25778](https://github.com/containers/podman/issues/25778)). - Quadlet `.container` files now support a new key, `HttpProxy`, to disable the automatic forwarding of HTTP proxy options from the host into the container ([#26925](https://github.com/containers/podman/issues/26925)). - Quadlet `.pod` files now support a new key, `StopTimeout`, to configure the stop timeout for the pod ([#27120](https://github.com/containers/podman/issues/27120)). - Quadlet `.build` files now support two new keys, `BuildArg` and `IgnoreFile`, to specify build arguments and an ignore file ([#27065](https://github.com/containers/podman/issues/27065) and [#27268](https://github.com/containers/podman/issues/27268)). - Quadlet `.kube` files now support multiple YAML files in a single `.kube` file. - Quadlet now supports templated dependencies for volumes and networks ([#25136](https://github.com/containers/podman/issues/25136)). - The `podman quadlet install` command now supports a new option, `--replace`, which will replace any existing Quadlet with a conflicting name ([#26930](https://github.com/containers/podman/issues/26930)). - The `podman quadlet print` command now has a new alias, `podman quadlet cat` ([#27296](https://github.com/containers/podman/issues/27296)). - The remote Podman client's `podman artifact remove` command now supports the `--all` option. - The `podman artifact add` command now supports a new option, `--replace`, which will replace any existing artifact with the given name ([#27082](https://github.com/containers/podman/issues/27082)). - The `podman artifact rm` command now supports a new option, `--ignore`, which will suppress errors when attempting to remove an artifact that does not exist ([#27084](https://github.com/containers/podman/issues/27084)). - The `podman artifact list` command now includes artifact creation time in its output ([#27314](https://github.com/containers/podman/issues/27314)). - The `podman artifact list --format` option now supports two new format keys, `VirtualSize`, returning the size of the artifact in integer bytes, and `CreatedAt`, returning the time the artifact was created as an RFC3339 timestamp (the existing `Size` and `Created` fields returned human-readable information) ([#27085](https://github.com/containers/podman/issues/27085)). - The `podman artifact inspect` command now supports a new option, `--format`, to return specific information about an artifact with user-specified formatting ([#27112](https://github.com/containers/podman/issues/27112)). ### Changes - In preparation for a planned removal of the BoltDB database in Podman 6.0, a warning has been added for installations still using BoltDB. These warnings were added in Podman 5.6, but were not visible by default; they now are. They can be suppressed with the `SUPPRESS_BOLTDB_WARNING=true` environment variable. - A new Windows installer has been introduced with a simpler single MSI architecture that supports both user-scope (no admin required) and machine-scope installations. Note: To use the new installer, users must uninstall existing Podman installations before using the new installer, but all containers, images, machines, and other data will be preserved. The old installer is still provided to ensure backwards compatibility, though it will be removed in a future release ([#22994](https://github.com/containers/podman/issues/22994) and [#25968](https://github.com/containers/podman/issues/25968)). - Podman now requires Go 1.24. - When the `-p`/`--publish` and `--network=ns:/path` options are used together when creating a container, Podman will not warn that the `-p` option will be ignored as an existing namespace is in use (this has always been the case, but Podman now prints a warning about it) ([#26663](https://github.com/containers/podman/issues/26663)). - The `podman stats` command now provides additional information about container resource utilization when run on FreeBSD. - Shell autocompletion has been enabled for the `--sysctl` option to `podman create` and `podman run`, and the `--interface-name` option to `podman network create`. - Artifacts created by Podman now include a creation timestamp by default, stored in the `org.opencontainers.image.created` annotation ([#27081](https://github.com/containers/podman/issues/27081)). - The `podman inspect` command can now inspect artifacts. - The `podman artifact add` command can now override the `org.opencontainers.image.title` annotation in created artifacts. - Podman can now optionally be built with Sequoia-PGP support. When so built, the `--sign-by-sq-fingerprint` option allows signing images using Seqoia-PGP keys. ### Bugfixes - Fixed a bug where the `--filter ancestor=` option to `podman ps` required complete matches, unlike Docker (which matched substrings) ([#26623](https://github.com/containers/podman/issues/26623)). - Fixed a bug where the `--filter label=` option to `podman events` did not support key-only matches (as `podman os --filter label=` does) ([#26702](https://github.com/containers/podman/issues/26702)). - Fixed a bug where Quadlet could panic when a `Mount` was given without a `source` being specified. - Fixed a bug where Quadlet would fail to generate for a `.build` file when a systemd specifier was used in the `[Build]` section ([#26746](https://github.com/containers/podman/issues/26746)). - Fixed a bug where the `podman info` command could panic when `/proc/sys/fs/binfmt_misc` was not mounted. - Fixed a bug where the remote Podman client could lose some initial bytes of output from attach sessions (`podman run`, `podman exec`, `podman attach`) due to a race condition ([#26951](https://github.com/containers/podman/issues/26951)). - Fixed a bug where the `podman build` command was ignoring SBOM related options ([#23915](https://github.com/containers/podman/issues/23915)). - Fixed a bug where the `--userns=ns:/path` option to `podman create` and `podman run` was broken with runc 1.1.11 and higher ([#27148](https://github.com/containers/podman/issues/27148)). - Fixed a bug where `podman machine` on Windows would always re-pull machine images when using the WSL provider, even if an the image had already been pulled and was present on disk. ### API - Added a new API endpoint to list quadlets (`GET /libpod/quadlets/json`). - The Compat Inspect endpoint for Images no longer includes the `ContainerConfig` field. To access image configuration, use the `Config` field instead. This matches changes made by Docker in the v1.45 API. - Fixed a bug where the Stats and Commit endpoints for Containers (compat & libpod), the Push, Commit, Push, and Pull endpoints for Images (compat & libpod), and the Push endpoint for Manifests (libpod) were not returning a `Content-Type` header. ### Misc - Error messages returned when an incomplete `--device` option (for example `--device /dev/fuse::`) is passed to `podman create` or `podman run` have been improved. - Updated Buildah to v1.42.0 - Updated the containers/image library to v5.38.0 - Updated the containers/storage library to v1.61.0 - Updated the containers/common library to v0.66.0 - The containers/image, containers/storage, and containers/common libraries are now sourced from the [containers/container-libs](https://github.com/containers/container-libs/) monorepo.

1 0

Podman Community Cabal Meeting next Tues, Nov 4, 2025 at 11:00 a.m. EST (UTC-5).
by Tom Sweeney 30 Oct '25

30 Oct '25

Hi All! The Podman Community Cabal Meeting is next Tuesday, November 4, 2025, at 11:00 a.m. EST (UTC-5). Note, the US is dropping out of Daylight savings time over the weekend. Also, we are full on with Zoom going forward, the link for that is in the agenda. We generally discuss design changes here, and the agenda is wide open for now; add a topic and join us! Agenda: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both#podman#opensource t

1 0

Podman candidate v5.7.0-rc2 Released
by container.tools.ci＠gmail.com 30 Oct '25

30 Oct '25

Hi all, Podman candidate v5.7.0-rc2 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.7.0-rc2 Release candidate Notes: -------------- ### Features - The remote Podman client and `podman system service` API server now support encrypting connections with TLS and mTLS, including client authentication by certificate ([#24583](https://github.com/containers/podman/issues/24583)). - The `podman system connection add` command can now create connections to TCP sockets with TLS and mTLS encryption. - The `podman run` and `podman create` commands now support two new options, `--creds` and `--cert-dir`, to manage logging into registries to pull images. - The `podman kube play` and `podman kube down` commands can now accept multiple files as input, creating or removing more than one pod or deployment with the same command ([#26274](github.com/containers/podman/issues/26274)). - The `podman kube play` command now supports a new option, `--no-pod-prefix`, to disable prefixing container names with pod names. Please note that this can cause pods to fail to create if the pod shares a name with a container ([#26396](https://github.com/containers/podman/issues/26396)). - The `podman machine init` command now supports a new option, `--tls-verify`, to control whether the machine image can be pulled from registries without a trusted TLS certificate, with the default being `true` (TLS verification on) ([#26517](https://github.com/containers/podman/issues/26517)). - When running the `podman image load` and `podman build` commands against a `podman machine` VM, if the path being loaded or built is shared into the VM, Podman will load it from the VM's filesystem instead of streaming the data through the REST API, improving performance ([#26321](https://github.com/containers/podman/issues/26321)). - A default location for container log files when using the `k8s-file` log driver can now be specified with the `log_path` option in `containers.conf`. - Default flags for the OCI runtime can now be set with the `runtimes_flags` option in `containers.conf`. - The `podman artifact remove` command can now accept multiple arguments, for example, `podman artifact rm artifact1 artifact2`. - The `podman wait` command now supports a new option, `--return-on-first`, which causes `podman wait` to return after *any* container matches the condition, as opposed to waiting for *all* containers to match ([#26691](https://github.com/containers/podman/issues/26691)). - The `podman container restore` command now supports a new option, `--tcp-close`, allowing containers with active TCP connections to be restored multiple times. - Quadlet now features support for a new file type, `.artifact`, allowing OCI artifacts to be managed with Quadlet ([#25778](https://github.com/containers/podman/issues/25778)). - Quadlet `.container` files now support a new key, `HttpProxy`, to disable the automatic forwarding of HTTP proxy options from the host into the container ([#26925](https://github.com/containers/podman/issues/26925)). - Quadlet `.pod` files now support a new key, `StopTimeout`, to configure the stop timeout for the pod ([#27120](https://github.com/containers/podman/issues/27120)). - Quadlet `.build` files now support two new keys, `BuildArg` and `IgnoreFile`, to specify build arguments and an ignore file ([#27065](https://github.com/containers/podman/issues/27065) and [#27268](https://github.com/containers/podman/issues/27268)). - Quadlet `.kube` files now support multiple YAML files in a single `.kube` file. - Quadlet now supports templated dependencies for volumes and networks ([#25136](https://github.com/containers/podman/issues/25136)). - The `podman quadlet install` command now supports a new option, `--replace`, which will replace any existing Quadlet with a conflicting name ([#26930](https://github.com/containers/podman/issues/26930)). - The `podman quadlet print` command now has a new alias, `podman quadlet cat` ([#27296](https://github.com/containers/podman/issues/27296)). - The remote Podman client's `podman artifact remove` command now supports the `--all` option. - The `podman artifact add` command now supports a new option, `--replace`, which will replace any existing artifact with the given name ([#27082](https://github.com/containers/podman/issues/27082)). - The `podman artifact rm` command now supports a new option, `--ignore`, which will suppress errors when attempting to remove an artifact that does not exist ([#27084](https://github.com/containers/podman/issues/27084)). - The `podman artifact list` command now includes artifact creation time in its output ([#27314](https://github.com/containers/podman/issues/27314)). - The `podman artifact list --format` option now supports two new format keys, `VirtualSize`, returning the size of the artifact in integer bytes, and `CreatedAt`, returning the time the artifact was created as an RFC3339 timestamp (the existing `Size` and `Created` fields returned human-readable information) ([#27085](https://github.com/containers/podman/issues/27085)). - The `podman artifact inspect` command now supports a new option, `--format`, to return specific information about an artifact with user-specified formatting ([#27112](https://github.com/containers/podman/issues/27112)). ### Changes - In preparation for a planned removal of the BoltDB database in Podman 6.0, a warning has been added for installations still using BoltDB. These warnings were added in Podman 5.6, but were not visible by default; they now are. They can be suppressed with the `SUPPRESS_BOLTDB_WARNING=true` environment variable. - A new Windows installer has been introduced with a simpler single MSI architecture that supports both user-scope (no admin required) and machine-scope installations. Note: To use the new installer, users must uninstall existing Podman installations before using the new installer, but all containers, images, machines, and other data will be preserved. The old installer is still provided to ensure backwards compatibility, though it will be removed in a future release ([#22994](https://github.com/containers/podman/issues/22994) and [#25968](https://github.com/containers/podman/issues/25968)). - Podman now requires Go 1.24. - When the `-p`/`--publish` and `--network=ns:/path` options are used together when creating a container, Podman will not warn that the `-p` option will be ignored as an existing namespace is in use (this has always been the case, but Podman now prints a warning about it) ([#26663](https://github.com/containers/podman/issues/26663)). - The `podman stats` command now provides additional information about container resource utilization when run on FreeBSD. - Shell autocompletion has been enabled for the `--sysctl` option to `podman create` and `podman run`, and the `--interface-name` option to `podman network create`. - Artifacts created by Podman now include a creation timestamp by default, stored in the `org.opencontainers.image.created` annotation ([#27081](https://github.com/containers/podman/issues/27081)). - The `podman inspect` command can now inspect artifacts. - The `podman artifact add` command can now override the `org.opencontainers.image.title` annotation in created artifacts. - Podman can now optionally be built with Sequoia-PGP support. When so built, the `--sign-by-sq-fingerprint` option allows signing images using Seqoia-PGP keys. ### Bugfixes - Fixed a bug where the `--filter ancestor=` option to `podman ps` required complete matches, unlike Docker (which matched substrings) ([#26623](https://github.com/containers/podman/issues/26623)). - Fixed a bug where the `--filter label=` option to `podman events` did not support key-only matches (as `podman os --filter label=` does) ([#26702](https://github.com/containers/podman/issues/26702)). - Fixed a bug where Quadlet could panic when a `Mount` was given without a `source` being specified. - Fixed a bug where Quadlet would fail to generate for a `.build` file when a systemd specifier was used in the `[Build]` section ([#26746](https://github.com/containers/podman/issues/26746)). - Fixed a bug where the `podman info` command could panic when `/proc/sys/fs/binfmt_misc` was not mounted. - Fixed a bug where the remote Podman client could lose some initial bytes of output from attach sessions (`podman run`, `podman exec`, `podman attach`) due to a race condition ([#26951](https://github.com/containers/podman/issues/26951)). - Fixed a bug where the `podman build` command was ignoring SBOM related options ([#23915](https://github.com/containers/podman/issues/23915)). - Fixed a bug where the `--userns=ns:/path` option to `podman create` and `podman run` was broken with runc 1.1.11 and higher ([#27148](https://github.com/containers/podman/issues/27148)). ### API - Added a new API endpoint to list quadlets (`GET /libpod/quadlets/json`). - The Compat Inspect endpoint for Images no longer includes the `ContainerConfig` field. To access image configuration, use the `Config` field instead. This matches changes made by Docker in the v1.45 API. - Fixed a bug where the Stats and Commit endpoints for Containers (compat & libpod), the Push, Commit, Push, and Pull endpoints for Images (compat & libpod), and the Push endpoint for Manifests (libpod) were not returning a `Content-Type` header. ### Misc - Error messages returned when an incomplete `--device` option (for example `--device /dev/fuse::`) is passed to `podman create` or `podman run` have been improved. - Updated Buildah to v1.42.0 - Updated the containers/image library to v5.38.0 - Updated the containers/storage library to v1.61.0 - Updated the containers/common library to v0.66.0 - The containers/image, containers/storage, and containers/common libraries are now sourced from the [containers/container-libs](https://github.com/containers/container-libs/) monorepo.

1 0