- Podman - Podman List Archives

Podman Community meeting in two weeks! Tues, April 1, 2025, 11:00 a.m. EDT (UTC-4)
by Tom Sweeney 18 Mar '25

18 Mar '25

Hi All! Two weeks from now, on Tuesday, April 1, 2025 at 11:00 am EDT (UTC-4), the Podman Community Meeting will be going on. We don't have any topics at the moment, so it's a great time to add your demo to our agenda! Hope to see you there!https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w?both t

1 0

Podman v5.4.1 Released
by Do Not Reply 11 Mar '25

11 Mar '25

Hi all, Podman v5.4.1 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.4.1 Release Notes: -------------- ### Bugfixes - Fixed a bug where volume quotas were not being applied ([#25368](https://github.com/containers/podman/issues/25368)). - Fixed a bug where the `--pid-limit=-1` option did not function properly with containers using the `runc` OCI runtime. - Fixed a bug where the `podman artifact pull` command did not respect the `--retry-delay` option. - Fixed a bug where Podman would leak a file and directory for every container created. - Fixed a bug where the `podman wait` command would sometimes error when waiting for a container set to auto-remove. - Fixed a bug where Quadlet `.kube` units would not report an error (and stay running) even when a pod failed to start ([#20667](https://github.com/containers/podman/issues/20667)). ### API - Fixed a bug where the Compat DF endpoint did not correctly report total size of all images. ### Misc - Updated Buildah to v1.39.2 - Updated the containers/common library to v0.62.1 - Updated the containers/image library to v5.34.1 This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

Podman v5.4.0 Released
by Do Not Reply 11 Feb '25

11 Feb '25

Hi all, Podman v5.4.0 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.4.0 Release Notes: -------------- ### Features - A preview of Podman's support for OCI artifacts has been added through the `podman artifact` suite of commands, including `add`, `inspect`, `ls`, `pull`, `push`, and `rm`. This support is very early and not fully complete, and the command line interface for these tools has not been finalized. We welcome feedback on the new artifact experience through our issue tracker! - The `podman update` command now supports a wide variety of options related to healthchecks (including `--health-cmd` to define a new healthcheck and `--no-healthcheck` to disable an existing healthcheck), allowing healthchecks to be added to, removed from, and otherwise updated on existing containers. You can find full details on the 15 added options in the manpage. - The `--mount type=volume` option for the `podman run`, `podman create`, and `podman volume create` commands now supports a new option, `subpath=`, to make only a subset of the volume visible in the container ([#20661](https://github.com/containers/podman/issues/20661)). - The `--userns=keep-id` option for the `podman run`, `podman create`, and `podman pod create` commands now supports a new option, `--userns=keep-id:size=`, to configure the size of the user namespace ([#24387](https://github.com/containers/podman/issues/24837)). - The `podman kube play` command now supports Container Device Interface (CDI) devices ([#17833](https://github.com/containers/podman/issues/17833)). - The `podman machine init` command now supports a new option, `--playbook`, to run an Ansible playbook in the created VM on first boot for initial configuration. - Quadlet `.pod` files now support a new field, `ShmSize`, to specify the size of the pod's shared SHM ([#22915](https://github.com/containers/podman/issues/22915)). - The `podman run`, `podman create`, and `podman pod create` commands now support a new option, `--hosts-file`, to define the base file used for `/etc/hosts` in the container. - The `podman run`, `podman create`, and `podman pod create` commands now support a new option, `--no-hostname`, which disables the creation of `/etc/hostname` in the container ([#25002](https://github.com/containers/podman/issues/25002)). - The `podman network create` command now supports a new option for `bridge` networks, `--opt mode=unmanaged`, which allows Podman to use an existing network bridge on the system without changes. - The `--network` option to `podman run`, `podman create`, and `podman pod create` now accepts a new option for `bridge` networks, `host_interface_name`, which specifies a name for the network interface created outside the container. - The `podman manifest rm` command now supports a new option, `--ignore`, to not error when removing manifests that do not exist. - The `podman system prune` command now supports a new option, `--build`, to remove build containers leftover from prematurely terminated builds. - The `podman events` command now generates events for the creation and removal of networks ([#24032](https://github.com/containers/podman/issues/24032)). ### Breaking Changes - Due to a lack of availability of hardware to test on, the Podman maintainers are no longer capable of providing full support for Podman on Intel Macs. Binaries and machine images will still be produced, and pull requests related to MacOS on Intel systems will still be merged, but bugs will be fixed on a best effort basis only. We welcome any potential new maintainers who would be able to assist in restoring full support. - Quadlet previously incorrectly allowed `:` as a character to define comments. This was a mistake; developer intent and documentation was that `#` and `;` were to be used as comment characters instead, matching systemd. This has been corrected, and semicolons now define comments instead of colons. ### Changes - Podman now passes container hostnames to Netavark, which will use them for any DHCP requests for the container. - Partial pulls of `zstd:chunked` images now only happen for images that have a `RootFS.DiffID` entry in the image's OCI config JSON, and require the layer contents to match. This resolves issues with image ID ambiguity when partial pulls were enabled. - Packagers can now set the `BUILD_ORIGIN` environment variable when building podman from the `Makefile`. This provides information on who built the Podman binary, and is displayed in `podman version` and `podman info`. This will help upstream bug reports, allowing maintainers to trace how and where the binary was built and installed from. ### Bugfixes - Fixed a bug where `podman machine` VMs on WSL could fail to start when using usermode networking could fail to start due to a port conflict ([#20327](https://github.com/containers/podman/issues/20327)). - Fixed a bug where overlay mounts could not be made at paths where the image specifies a volume ([#24555](https://github.com/containers/podman/issues/24555)). - Fixed a bug where the `podman build` command did not honor the `no_pivot_root` setting from `containers.conf` ([#24546](https://github.com/containers/podman/issues/24546)). - Fixed a bug where volumes would have the wrong permissions if `podman cp` was used to copy into a fresh volume in a container that had never been started. - Fixed a bug where using `podman cp` to copy into a named volume requiring a mount (image volumes, volumes backed by a volume plugin, or other volumes with options) would fail when the container being copied into was stopped. - Fixed a bug where rlimits would be set incorrectly when Podman was run as root but without `CAP_SYS_RESOURCE` ([#24692](https://github.com/containers/podman/issues/24692)). - Fixed a bug where the `podman stats --all` command would fail if a container started with `--cgroups=none` was present ([#24632](https://github.com/containers/podman/issues/24632)). - Fixed a bug where the `podman info` command would only return details on one image store even if additional image stores were configured in `storage.conf`. - Fixed a bug where the `podman update` command could reset resource limits that were not being modified to default ([#24610](https://github.com/containers/podman/issues/24610)). - Fixed a bug where the remote Podman client's `podman update` command could not update resource limits on devices mounted into the container ([#24734](https://github.com/containers/podman/issues/24734)). - Fixed a bug where the `podman manifest annotate` command could panic when the `--index` option was used ([#24750](https://github.com/containers/podman/issues/24750)). - Fixed a bug where a Quadlet container reusing another container's network could cause errors if the second container was not already running. - Fixed a bug where Quadlet files containing lines with a trailing backslash could cause an infinite loop during parsing ([#24810](https://github.com/containers/podman/issues/24810)). - Fixed a bug where Quadlet would, when run as a non-root user, not generate for files in subfolders of `/etc/containers/systemd/users/` ([#24783](https://github.com/containers/podman/issues/24783)). - Fixed a bug where values in Quadlet files containing octal escape sequences were incorrectly unescaped. - Fixed a bug where `podman generate kube` could generate persistent volumes with mixed-case names or names containing an underscore, which are not supported by Kubernetes ([#16542](https://github.com/containers/podman/issues/16542)). - Fixed a bug where the `ptmxmode` option to `--mount type=devpts` did not function. - Fixed a bug where shell completion on Windows would include `.exe` in the executable name, breaking completion on some shells. - Fixed a bug where the output of `podman inspect` on containers did not include the ID of the network the container was joined to, improving Docker compatibility ([#24910](https://github.com/containers/podman/issues/24910)). - Fixed a bug where containers created with the remote API incorrectly included a create command ([#25026](https://github.com/containers/podman/issues/25026)). - Fixed a bug where it was possible to specify the `libkrun` backend for VMs on Intel Macs (`libkrun` only supports Arm systems). - Fixed a bug where `libkrun` and `applehv` VMs from `podman machine` could be started at the same time on Macs ([#25112](https://github.com/containers/podman/issues/25112)). - Fixed a bug where `podman exec` commands could not detach from the exec session using the detach keys ([#24895](https://github.com/containers/podman/issues/24895)). - Fixed a bug where Podman would fail to start due to a database configuration mismatch when certain fields were configured to the empty string ([#24738](https://github.com/containers/podman/issues/24738)). ### API - The Compat and Libpod Build APIs for Images now support a new query parameter, `nohosts`, which (when set to true) does not create `/etc/hosts` in the image when building. - Fixed a bug where the Compat Create API for Containers did not honor CDI devices, preventing (among other things) the use of GPUs with `docker compose` ([#19338](https://github.com/containers/podman/issues/19338)). ### Misc - The Docker alias script has been fixed to better handle variable substitution. - Fixed a bug where `podman-restart.service` functioned incorrectly when no containers were present. - Updated Buildah to v1.39.0 - Updated the containers/common library to v0.62.0 - Updated the containers/storage library to v1.57.1 - Updated the containers/image library to v5.34.0 This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

Podman candidate v5.4.0-rc3 Released
by Do Not Reply 05 Feb '25

05 Feb '25

Hi all, Podman candidate v5.4.0-rc3 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.4.0-rc3 Release candidate Notes: -------------- This is the final release candidate for Podman v5.4.0. Preliminary release notes follow: ### Features - A preview of Podman's support for OCI artifacts has been added through the `podman artifact` suite of commands, including `add`, `inspect`, `ls`, `pull`, `push`, and `rm`. This support is very early and not fully complete, and the command line interface for these tools has not been finalized. We welcome feedback on the new artifact experience through our issue tracker! - The `podman update` command now supports a wide variety of options related to healthchecks (including `--health-cmd` to define a new healthcheck and `--no-healthcheck` to disable an existing healthcheck), allowing healthchecks to be added to, removed from, and otherwise updated on existing containers. You can find full details on the 15 added options in the manpage. - The `--mount type=volume` option for the `podman run`, `podman create`, and `podman volume create` commands now supports a new option, `subpath=`, to make only a subset of the volume visible in the container ([#20661](https://github.com/containers/podman/issues/20661)). - The `--userns=keep-id` option for the `podman run`, `podman create`, and `podman pod create` commands now supports a new option, `--userns=keep-id:size=`, to configure the size of the user namespace ([#24387](https://github.com/containers/podman/issues/24837)). - The `podman kube play` command now supports Container Device Interface (CDI) devices ([#17833](https://github.com/containers/podman/issues/17833)). - The `podman machine init` command now supports a new option, `--playbook`, to run an Ansible playbook in the created VM on first boot for initial configuration. - Quadlet `.pod` files now support a new field, `ShmSize`, to specify the size of the pod's shared SHM ([#22915](https://github.com/containers/podman/issues/22915)). - The `podman run`, `podman create`, and `podman pod create` commands now support a new option, `--hosts-file`, to define the base file used for `/etc/hosts` in the container. - The `podman run`, `podman create`, and `podman pod create` commands now support a new option, `--no-hostname`, which disables the creation of `/etc/hostname` in the container ([#25002](https://github.com/containers/podman/issues/25002)). - The `podman network create` command now supports a new option for `bridge` networks, `--opt mode=unmanaged`, which allows Podman to use an existing network bridge on the system without changes. - The `--network` option to `podman run`, `podman create`, and `podman pod create` now accepts a new option for `bridge` networks, `host_interface_name`, which specifies a name for the network interface created outside the container. - The `podman manifest rm` command now supports a new option, `--ignore`, to not error when removing manifests that do not exist. - The `podman system prune` command now supports a new option, `--build`, to remove build containers leftover from prematurely terminated builds. - The `podman events` command now generates events for the creation and removal of networks ([#24032](https://github.com/containers/podman/issues/24032)). ### Breaking Changes - Due to a lack of availability of hardware to test on, the Podman maintainers are no longer capable of providing full support for Podman on Intel Macs. Binaries and machine images will still be produced, and pull requests related to MacOS on Intel systems will still be merged, but bugs will be fixed on a best effort basis only. We welcome any potential new maintainers who would be able to assist in restoring full support. - Quadlet previously incorrectly allowed `:` as a character to define comments. This was a mistake; developer intent and documentation was that `#` and `;` were to be used as comment characters instead, matching systemd. This has been corrected, and semicolons now define comments instead of colons. ### Changes - Podman now passes container hostnames to Netavark, which will use them for any DHCP requests for the container. - Partial pulls of `zstd:chunked` images now only happen for images that have a `RootFS.DiffID` entry in the image's OCI config JSON, and require the layer contents to match. This resolves issues with image ID ambiguity when partial pulls were enabled. - Packagers can now set the `BUILD_ORIGIN` environment variable when building podman from the `Makefile`. This provides information on who built the Podman binary, and is displayed in `podman version` and `podman info`. This will help upstream bug reports, allowing maintainers to trace how and where the binary was built and installed from. ### Bugfixes - Fixed a bug where `podman machine` VMs on WSL could fail to start when using usermode networking could fail to start due to a port conflict ([#20327](https://github.com/containers/podman/issues/20327)). - Fixed a bug where overlay mounts could not be made at paths where the image specifies a volume ([#24555](https://github.com/containers/podman/issues/24555)). - Fixed a bug where the `podman build` command did not honor the `no_pivot_root` setting from `containers.conf` ([#24546](https://github.com/containers/podman/issues/24546)). - Fixed a bug where volumes would have the wrong permissions if `podman cp` was used to copy into a fresh volume in a container that had never been started. - Fixed a bug where using `podman cp` to copy into a named volume requiring a mount (image volumes, volumes backed by a volume plugin, or other volumes with options) would fail when the container being copied into was stopped. - Fixed a bug where rlimits would be set incorrectly when Podman was run as root but without `CAP_SYS_RESOURCE` ([#24692](https://github.com/containers/podman/issues/24692)). - Fixed a bug where the `podman stats --all` command would fail if a container started with `--cgroups=none` was present ([#24632](https://github.com/containers/podman/issues/24632)). - Fixed a bug where the `podman info` command would only return details on one image store even if additional image stores were configured in `storage.conf`. - Fixed a bug where the `podman update` command could reset resource limits that were not being modified to default ([#24610](https://github.com/containers/podman/issues/24610)). - Fixed a bug where the remote Podman client's `podman update` command could not update resource limits on devices mounted into the container ([#24734](https://github.com/containers/podman/issues/24734)). - Fixed a bug where the `podman manifest annotate` command could panic when the `--index` option was used ([#24750](https://github.com/containers/podman/issues/24750)). - Fixed a bug where a Quadlet container reusing another container's network could cause errors if the second container was not already running. - Fixed a bug where Quadlet files containing lines with a trailing backslash could cause an infinite loop during parsing ([#24810](https://github.com/containers/podman/issues/24810)). - Fixed a bug where Quadlet would, when run as a non-root user, not generate for files in subfolders of `/etc/containers/systemd/users/` ([#24783](https://github.com/containers/podman/issues/24783)). - Fixed a bug where values in Quadlet files containing octal escape sequences were incorrectly unescaped. - Fixed a bug where `podman generate kube` could generate persistent volumes with mixed-case names or names containing an underscore, which are not supported by Kubernetes ([#16542](https://github.com/containers/podman/issues/16542)). - Fixed a bug where the `ptmxmode` option to `--mount type=devpts` did not function. - Fixed a bug where shell completion on Windows would include `.exe` in the executable name, breaking completion on some shells. - Fixed a bug where the output of `podman inspect` on containers did not include the ID of the network the container was joined to, improving Docker compatibility ([#24910](https://github.com/containers/podman/issues/24910)). - Fixed a bug where containers created with the remote API incorrectly included a create command ([#25026](https://github.com/containers/podman/issues/25026)). - Fixed a bug where it was possible to specify the `libkrun` backend for VMs on Intel Macs (`libkrun` only supports Arm systems). - Fixed a bug where `libkrun` and `applehv` VMs from `podman machine` could be started at the same time on Macs ([#25112](https://github.com/containers/podman/issues/25112)). - Fixed a bug where `podman exec` commands could not detach from the exec session using the detach keys ([#24895](https://github.com/containers/podman/issues/24895)). ### API - The Compat and Libpod Build APIs for Images now support a new query parameter, `nohosts`, which (when set to true) does not create `/etc/hosts` in the image when building. - Fixed a bug where the Compat Create API for Containers did not honor CDI devices, preventing (among other things) the use of GPUs with `docker compose` ([#19338](https://github.com/containers/podman/issues/19338)). ### Misc - The Docker alias script has been fixed to better handle variable substitution. - Fixed a bug where `podman-restart.service` functioned incorrectly when no containers were present. - Updated Buildah to v1.39.0 - Updated the containers/common library to v0.62.0 - Updated the containers/storage library to v1.57.1 - Updated the containers/image library to v5.34.0 This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

podman container for an old SuSE Linux SLES 10.3
by Matthias Apitz 05 Feb '25

05 Feb '25

Hello, One of our customers is running an older version of our Lybrary Management System on top of an outdated Linux SUSE Linux Enterprise Server 10.3 (x86_64) and Oracle 10 (which for sure is not a good idea). I plan to try an update of the application servers to a more recent version which uses PostgreSQL 16.2 on top of SLES 15SP6. While we use a lot of podman containers with this recent version of SLES and PostgreSQL, I can't build a container for SLES 10: It says: $ podman build -t sles10-sp3-v41pl2 sles10-sp3-v41pl2 STEP 1/22: FROM registry.suse.com/suse/ltss/sle12.5/sles12sp5 Trying to pull registry.suse.com/suse/ltss/sle12.5/sles12sp5:latest... Error: creating build container: initializing source docker://registry.suse.com/suse/ltss/sle12.5/sles12sp5:latest: reading manifest latest in registry.suse.com/suse/ltss/sle12.5/sles12sp5: requested access to the resource is denied Any idea how to solve this? Thanks matthias -- Matthias Apitz, ✉ guru(a)unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub

3 2

Podman candidate v5.4.0-rc2 Released
by Do Not Reply 30 Jan '25

30 Jan '25

Hi all, Podman candidate v5.4.0-rc2 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.4.0-rc2 Release candidate Notes: -------------- This is the second release candidate for Podman v5.4.0. Preliminary release notes follow. ### Features - A preview of Podman's support for OCI artifacts has been added through the `podman artifact` suite of commands, including `add`, `inspect`, `ls`, `pull`, `push`, and `rm`. This support is very early and not fully complete, and the command line interface for these tools has not been finalized. We welcome feedback on the new artifact experience through our issue tracker! - The `podman update` command now supports a wide variety of options related to healthchecks (including `--health-cmd` to define a new healthcheck and `--no-healthcheck` to disable an existing healthcheck), allowing healthchecks to be added to, removed from, and otherwise updated on existing containers. You can find full details on the 15 added options in the manpage. - The `--mount type=volume` option for the `podman run`, `podman create`, and `podman volume create` commands now supports a new option, `subpath=`, to make only a subset of the volume visible in the container ([#20661](https://github.com/containers/podman/issues/20661)). - The `--userns=keep-id` option for the `podman run`, `podman create`, and `podman pod create` commands now supports a new option, `--userns=keep-id:size=`, to configure the size of the user namespace ([#24387](https://github.com/containers/podman/issues/24837)). - The `podman kube play` command now supports Container Device Interface (CDI) devices ([#17833](https://github.com/containers/podman/issues/17833)). - Quadlet `.pod` files now support a new field, `ShmSize`, to specify the size of the pod's shared SHM ([#22915](https://github.com/containers/podman/issues/22915)). - The `podman run`, `podman create`, and `podman pod create` commands now support a new option, `--hosts-file`, to define the base file used for `/etc/hosts` in the container. - The `podman run`, `podman create`, and `podman pod create` commands now support a new option, `--no-hostname`, which disables the creation of `/etc/hostname` in the container ([#25002](https://github.com/containers/podman/issues/25002)). - The `podman network create` command now supports a new option for `bridge` networks, `--opt mode=unmanaged`, which allows Podman to use an existing network bridge on the system without changes. - The `--network` option to `podman run`, `podman create`, and `podman pod create` now accepts a new option for `bridge` networks, `host_interface_name`, which specifies a name for the network interface created outside the container. - The `podman manifest rm` command now supports a new option, `--ignore`, to not error when removing manifests that do not exist. - The `podman system prune` command now supports a new option, `--build`, to remove build containers leftover from prematurely terminated builds. - The `podman events` command now generates events for the creation and removal of networks ([#24032](https://github.com/containers/podman/issues/24032)). ### Breaking Changes - Due to a lack of availability of hardware to test on, the Podman maintainers are no longer capable of providing full support for Podman on Intel Macs. Binaries and machine images will still be produced, and pull requests related to MacOS on Intel systems will still be merged, but bugs will be fixed on a best effort basis only. We welcome any potential new maintainers who would be able to assist in restoring full support. - Quadlet previously incorrectly allowed `:` as a character to define comments. This was a mistake; developer intent and documentation was that `#` and `;` were to be used as comment characters instead, matching systemd. This has been corrected, and semicolons now define comments instead of colons. ### Changes - Podman now passes container hostnames to Netavark, which will use them for any DHCP requests for the container. - Partial pulls of `zstd:chunked` images now only happen for images that have a `RootFS.DiffID` entry in the image's OCI config JSON, and require the layer contents to match. This resolves issues with image ID ambiguity when partial pulls were enabled. ### Bugfixes - Fixed a bug where `podman machine` VMs on WSL could fail to start when using usermode networking could fail to start due to a port conflict ([#20327](https://github.com/containers/podman/issues/20327)). - Fixed a bug where overlay mounts could not be made at paths where the image specifies a volume ([#24555](https://github.com/containers/podman/issues/24555)). - Fixed a bug where the `podman build` command did not honor the `no_pivot_root` setting from `containers.conf` ([#24546](https://github.com/containers/podman/issues/24546)). - Fixed a bug where volumes would have the wrong permissions if `podman cp` was used to copy into a fresh volume in a container that had never been started. - Fixed a bug where using `podman cp` to copy into a named volume requiring a mount (image volumes, volumes backed by a volume plugin, or other volumes with options) would fail when the container being copied into was stopped. - Fixed a bug where rlimits would be set incorrectly when Podman was run as root but without `CAP_SYS_RESOURCE` ([#24692](https://github.com/containers/podman/issues/24692)). - Fixed a bug where the `podman stats --all` command would fail if a container started with `--cgroups=none` was present ([#24632](https://github.com/containers/podman/issues/24632)). - Fixed a bug where the `podman info` command would only return details on one image store even if additional image stores were configured in `storage.conf`. - Fixed a bug where the `podman update` command could reset resource limits that were not being modified to default ([#24610](https://github.com/containers/podman/issues/24610)). - Fixed a bug where the remote Podman client's `podman update` command could not update resource limits on devices mounted into the container ([#24734](https://github.com/containers/podman/issues/24734)). - Fixed a bug where the `podman manifest annotate` command could panic when the `--index` option was used ([#24750](https://github.com/containers/podman/issues/24750)). - Fixed a bug where a Quadlet container reusing another container's network could cause errors if the second container was not already running. - Fixed a bug where Quadlet files containing lines with a trailing backslash could cause an infinite loop during parsing ([#24810](https://github.com/containers/podman/issues/24810)). - Fixed a bug where Quadlet would, when run as a non-root user, not generate for files in subfolders of `/etc/containers/systemd/users/` ([#24783](https://github.com/containers/podman/issues/24783)). - Fixed a bug where values in Quadlet files containing octal escape sequences were incorrectly unescaped. - Fixed a bug where `podman generate kube` could generate persistent volumes with mixed-case names or names containing an underscore, which are not supported by Kubernetes ([#16542](https://github.com/containers/podman/issues/16542)). - Fixed a bug where the `ptmxmode` option to `--mount type=devpts` did not function. - Fixed a bug where shell completion on Windows would include `.exe` in the executable name, breaking completion on some shells. - Fixed a bug where the output of `podman inspect` on containers did not include the ID of the network the container was joined to, improving Docker compatibility ([#24910](https://github.com/containers/podman/issues/24910)). - Fixed a bug where containers created with the remote API incorrectly included a create command ([#25026](https://github.com/containers/podman/issues/25026)). - Fixed a bug where it was possible to specify the `libkrun` backend for VMs on Intel Macs (`libkrun` only supports Arm systems). ### API - The Compat and Libpod Build APIs for Images now support a new query parameter, `nohosts`, which (when set to true) does not create `/etc/hosts` in the image when building. ### Misc - The Docker alias script has been fixed to better handle variable substitution. - Fixed a bug where `podman-restart.service` functioned incorrectly when no containers were present. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

Podman Community Meeting, Tuesday February 4, 2025 at 11:00 a.m. EST (UTC-5)
by Tom Sweeney 28 Jan '25

28 Jan '25

Hi All! The Podman Community Meeting will happen a week from now at 11:00 am EST (UTC-5). At the moment, we have plenty of room for topics if you'd like to add one to our agenda! A nice demo of what you're working on? A topic you'd like to discuss? Add it to the agenda! https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w?both Hope to see you there! t

1 0

access to an existing SuSE container image is denied
by Matthias Apitz 27 Jan '25

27 Jan '25

Hello, I'm trying to use LTSS container from SuSE registry, this one https://registry.suse.com/repositories/suse-ltss-sle12-5-sles12sp5 The instructions in https://documentation.suse.com/container/all/single-html/Container-guide/#c… say how to login: $ cat /etc/zypp/credentials.d/SCCcredentials username=SCC_xxxxxxxxx password=85xxxxxxxxx ... $ echo '85xxxxxxxx' | podman login -u 'SCC_xxxxxxxx' --password-stdin registry.suse.com Login Succeeded! This login creates a file $ ls -l /run/user/1000/containers/auth.json -rw------- 1 cups root 133 27. Jan 07:41 /run/user/1000/containers/auth.json I copied this over to: $ cp -p /run/user/1000/containers/auth.json ~/.config/containers/auth.json and set: $ export REGISTRY_AUTH_FILE=/home/cups/.config/containers/auth.json but it does not works, at least not how I would expect it: $ podman build -t sles10-sp3-v41pl2 sles10-sp3-v41pl2 STEP 1/22: FROM registry.suse.com/suse/ltss/sle12.5/sles12sp5:latest Trying to pull registry.suse.com/suse/ltss/sle12.5/sles12sp5:latest... Error: creating build container: initializing source docker://registry.suse.com/suse/ltss/sle12.5/sles12sp5:latest: reading manifest latest in registry.suse.com/suse/ltss/sle12.5/sles12sp5: requested access to the resource is denied also this doesn't work: $ podman build --creds=SCC_xxxxxxxx:85xxxxxxxx -t sles10-sp3-v41pl2 sles10-sp3-v41pl2 https://registry.suse.com/repositories/suse-ltss-sle12-5-sles12sp5 gives: registry.suse.com/suse/ltss/sle12.5/sles12sp5:latest but inspect says: $ podman inspect registry.suse.com/suse/ltss/sle12.5/sles12sp5:latest Error: no such object: "registry.suse.com/suse/ltss/sle12.5/sles12sp5:latest" What I'm doing wrong here? Thanks matthias -- Matthias Apitz, ✉ guru(a)unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub

3 3

Podman candidate v5.4.0-rc1 Released
by Do Not Reply 23 Jan '25

23 Jan '25

Hi all, Podman candidate v5.4.0-rc1 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.4.0-rc1 Release candidate Notes: -------------- This is the first release candidate of Podman v5.4.0. Full release notes will be available with RC2 next week. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

How to overcome bind mount nobody:nogroup ownership in a rootless container?
by jklaiho＠iki.fi 22 Jan '25

22 Jan '25

I've got a rootless, quadlet-based container running with an unprivileged local user called "app", with UID 1017 and GID 1020. In addition, this user belongs to group IDs 1002 ("sftp-only") and 1003 ("sftp-reader"). There's a host directory /srv/sftp-home, owned by root with its group set to sftp-only, 0750 permissions. It has a bunch of subdirectories, owned by individual SFTP connecting users, but with the group set to sftp-reader on all of them, 0750 permissions also. The app user is able to read all of these directories via the host group membership. In the quadlet config for the service running as this user, I have these lines: [Container] # container root is my host "app" user UIDMap=0:0:1 # For apt-get to work inside the container UIDMap=42:1:1 # container root group is my host "app" group GIDMap=0:0:1 # For apt-get to work inside the container GIDMap=65534:1:1 # Probably irrelevant here, but mentioned just in case NoNewPrivileges=true Mount=type=bind,source=/srv/sftp-home,target=/srv/sftp-home All other quadlet file contents have been omitted here, but there should be nothing else that's related to this issue there. Within the container, the bind mounted /srv/sftp-home is owned by nobody:nogroup, and the in-container root user is unable to access them despite the underlying host user being able to access the bind mount source directory. What can be done to fix this? Podman version 5.2.5.

2 1