June 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 Community Cabal, Tuesday July 1, 2025 at 11:00 a.m. EST (UTC-5)
by Neil Smith 30 Jun '25

30 Jun '25

Hi All! The Podman Community Meeting will happen tomorrow at 11:00 am EST (UTC-5). We have a great group of topics on our agenda! If you have a topic you'd like to discuss, please feel free to add it. https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?view Meeting will happen here - meet.google.com/xrq-uemd-bzy Hope to see you there! Neil -- *Neil Smith* (he, him, his) Senior Manager, Container Tools neil(a)redhat.com | 917-721-4167

1 0

Podman v5.5.2 Released
by Do Not Reply 24 Jun '25

24 Jun '25

Hi all, Podman v5.5.2 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.5.2 Release Notes: -------------- ### Security - This release addresses CVE-2025-6032, in which the TLS connection used to pull VM images for `podman machine` was, by default, not validated, allowing connections to servers with invalid certificates by default and potentially allowing a Man in the Middle attack. ### Bugfixes - Fixed a bug where Podman could panic after a reboot on systems with pods containing containers ([#26469](https://github.com/containers/podman/issues/26469)). This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

Running systemd in rootless container
by Михаил Иванов 14 Jun '25

14 Jun '25

Greetings! I'm trying to run systemd in rootless container as follows: podman run --interactive --tty --replace --name test --systemd always --privileged --entrypoint '[ "/usr/lib/systemd/systemd", "--system" ]' df785493a5e5 I'm getting the following error: systemd 252-46.el9_5.2.0.1 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) Detected virtualization podman. Detected architecture x86-64. Welcome to Rocky Linux 9.5 (Blue Onyx)! Failed to write /run/systemd/container, ignoring: Permission denied Failed to open '/sys/firmware/dmi/entries/11-0/raw', ignoring: Permission denied Failed to allocate manager object: Permission denied [!!!!!!] Failed to allocate manager object. Exiting PID 1... What I'm doing wrong here? My host system is debian/testing, podman version 5.4.2 Best regards, -- Michael Ivanov

3 3

Podman v5.5.1 Released
by Do Not Reply 05 Jun '25

05 Jun '25

Hi all, Podman v5.5.1 is now available. You may view the full details at https://github.com/containers/podman/releases/tag/v5.5.1 Release Notes: -------------- ### Bugfixes - Fixed a bug where containers mounting a volume to `/` could overmount important directories such as `/proc` causing start and/or runtime failures due to an issue with mount ordering ([#26161](https://github.com/containers/podman/issues/26161)). - Fixed a bug where Quadlet `.pod` units could fail to start due to their storage not being mounted ([#26190](https://github.com/containers/podman/issues/26190)). - Fixed a bug where containers joined to a network with DNS enabled would not include the host's search domains in their `resolv.conf` ([#24713](https://github.com/containers/podman/issues/24713)). - Fixed a bug where the `--dns-opt` option to `podman create`, `podman run`, and `podman pod create` would append options to the container's `resolv.conf`, instead of replacing them ([#22399](https://github.com/containers/podman/issues/22399)). - Fixed a bug where the `podman kube play` command would add an empty network alias for containers created with no name specified, causing Netavark to emit extraneous warnings. - Fixed a bug where the `podman system df` command would panic when one or more containers were created using a root filesystem (the `--rootfs` option to `podman create` and `podman run`) instead of from an image ([#26224](https://github.com/containers/podman/issues/26224)). - Fixed a bug where the `log_tag` field in `containers.conf` would override the `--log-opt tag=value` option to `podman create` and `podman run` ([#26236](https://github.com/containers/podman/issues/26236)). - Fixed a bug where the `podman volume rm` and `podman volume inspect` commands would incorrectly handle volume names containing the `_` character when the SQLite database backend was in use ([#26168](https://github.com/containers/podman/issues/26168)). - Fixed a bug where the Podman remote client on Windows was unable to mount local folders into containers using overlay mounts (`-v source:destination:O`) ([#25988](https://github.com/containers/podman/issues/25988)). ### API - Fixed a bug in the Libpod Create API for Containers where rlimits specified with a value of `-1` were causing errors, instead of being interpreted as the maximum possible value ([#24886](https://github.com/containers/podman/issues/24886)). - Fixed a bug in the Compat Create API for Containers where specifying an entrypoint of `[]` (an empty array) was ignored, instead of setting an empty entrypoint ([#26078](https://github.com/containers/podman/issues/26078)). ### Misc - Updated Buildah to v1.40.1 - Updated the containers/common library to v0.63.1 This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

1 0

Podman Community Meeting, Tuesday, June 3, 2025 at 11:00 a.m. EST (UTC-5)
by Matt Heon 02 Jun '25

02 Jun '25

Hi all, The Podman Community Meeting will happen tomorrow at 11:00 AM EST (UTC-5). We have several items on the agenda already, but if you'd like to add more - a demo of what you're working on, or a topic you'd like discussed - feel free to edit the agenda and add it. The agenda is located here: https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w?both Thanks, and hope to see you there! Matt Heon

1 0