January 2025 - Podman - Podman List Archives

# in environment ?
by lejeczek 09 Aug '25

09 Aug '25

Hi guys. Do you use # in your envs? I wonder if it's just me having issues with those. For a test, to reproduce the issue, 'ghost' web solution would be easy & quick: -> $ podman run -dt ...................... --env database__client=mysql --env database__connection__host=11.1.0.1 --env database__connection__user=ghostadm --env database__connection__password='xyz#admghost' --env database__connection__database=ghost_xyz --env url=https://ghost.xyz So far all I've tried with 'database__connection__password' failed, quoting &| escaping. I often use # - does anybody have a way to make it work? many thanks, L.

3 3

RunRoot & mistaken IDs
by lejeczek 03 Jul '25

03 Jul '25

Hi guys. I experience this: -> $ podman images WARN[0000] RunRoot is pointing to a path (/run/user/1007/containers) which is not writable. Most likely podman will fail. Error: creating events dirs: mkdir /run/user/1007: permission denied -> $ id uid=2001(podmania) gid=2001(podmania) groups=2001(podmania) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 I think it might have something to do with the fact that I changed UID for the user, but why would this be? How troubleshoot & fix it, ideally without system reboot? many thanks, L.

4 11

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

Podman v5.3.2 Released
by Do Not Reply 22 Jan '25

22 Jan '25

Hi all, Podman v5.3.2 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.3.2 Release Notes: -------------- ### Security - This release contains Buildah v1.38.1 which addresses [CVE-2024-11218](https://github.com/advisories/GHSA-5vpc-35f4-r8w6) ### Bugfixes - Fixed a bug where Quadlet `.build` files could create an invalid podman command line when `Pull=` was used ([#24599](https://github.com/containers/podman/issues/24599)). - Fixed a bug where the Mac installer did not install the Podman manpages ([#24756](https://github.com/containers/podman/issues/24756)). ### Misc - Updated Buildah to v1.38.1 - Updated the containers/common library to v0.61.1 - Updated the containers/storage library to v1.56.1 - Updated the containers/image library to v5.33.1 This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

Assigned ip address does not respond
by Michael Ivanov 14 Jan '25

14 Jan '25

Hallo, I'm trying to set up a container with fixed ip address. I have done the following: podman network create --subnet 10.89.16.0/24 testnet podman run . . . . --network testnet --ip 10.89.16.32 --publish 9094:9092 . . . . . Inside my container a service is listening on port 9092. When I exec into container, I can access service at port 9092 But when I'm trying to connect to 10.89.16.32:9094 from the host, connection hangs. 10.89.16.32 also cannot be pinged from host. When I inspect the network I get the following: island:other [master]> podman network inspect testnet | more [ { "name": "testnet", "id": "0fc4c960a787386f000c94760c47a27bf987e8c7900015a17686f1d49386764b", "driver": "bridge", "network_interface": "podman8", "created": "2025-01-13T23:12:33.065307139+03:00", "subnets": [ { "subnet": "10.89.16.0/24", "gateway": "10.89.16.1" } ], "ipv6_enabled": false, "internal": false, "dns_enabled": true, "ipam_options": { "driver": "host-local" }, "containers": { "20186a8598e92c5dea05d722f46651aa688543ee01cf6aa7a324e55ff631f0ee": { "name": "test", "interfaces": { "eth0": { "subnets": [ { "ipnet": "10.89.16.32/24", "gateway": "10.89.16.1" } ], "mac_address": "ca:60:49:9b:66:e8" } } } } } ] podman version is 5.3.1 (debian/sid), container is run in rootless mode. Best regards, -- Michael Ivanov

2 1