February 2024 - 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

shouldn't the current directory be the default context for "podman build"?
by Robert P. J. Day 12 Dec '24

12 Dec '24

"man podman-build" suggests that the context argument is optional: SYNOPSIS podman build [options] [context] podman image build [options] [context] ... If no context directory is specified, then Podman will assume the current working directory as the build context, which should contain the Containerfile. but if i have a directory with nothing but a Containerfile, i get: $ podman build Error: no context directory specified, and no containerfile specified $ OTOH, specifying context of current directory: $ podman build . STEP 1: FROM alpine:latest ... etc etc ... thoughts? rday

4 5

stopping podman container
by Matthias Apitz 26 Feb '24

26 Feb '24

Hello, I'm facing the following small issue while stopping a podman container on RedHat 8.9 and SuSE SLES 15SP4. Inside the container runs also a SuSE SLES 15SP4: $ podman run -d -p 2022:22 -p 28076:8076 -p 23045:3045 7c180cc3c676 c408e9d468cdebbc11a2d974ccf40e315fa724ada702e713359019a25b2b6882 ... $ podman stop c408e9d468cdebbc11a2d974ccf40e315fa724ada702e713359019a25b2b6882 WARN[0010] StopSignal SIGQUIT failed to stop container vibrant_bartik in 10 seconds, resorting to SIGKILL c408e9d468cdebbc11a2d974ccf40e315fa724ada702e713359019a25b2b6882 The Dockerfile which is used to build the container end with: $ tail -5 suse/Dockerfile EXPOSE 22 8076 3045 ENTRYPOINT /usr/local/bin/start.sh STOPSIGNAL SIGQUIT Any ideas what I do wrong? matthias -- Matthias Apitz, ✉ guru(a)unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub I am not at war with Russia. Я не воюю с Россией. Ich bin nicht im Krieg mit Russland.

3 5

podman stop -t -1 container-id issue
by Manvendra Bhangui 25 Feb '24

25 Feb '24

Hi, I have a container where I have my own program as init replacement. It takes the responsibility of shutting down all my services properly (one of them being MySQL). Sometimes some services need more than the default 10 seconds that podman stop command has before it resorts to SIGKILL. So while playing with various timeout, I get a strange result with I use -1 (supposed to be for infinite wait). Giving -1 results in immediate SIGKILL $ podman stop -t -1 indimail-mta WARN[0000] StopSignal SIGTERM failed to stop container indimail-mta in 18446744073709551615 seconds, resorting to SIGKILL indimail-mta Looks like unsigned 64 bit integer has been used for something which can have negative value -- Regards Manvendra - http://www.indimail.org GPG Pub Key http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC7CBC760014D250C

2 4

Podman on OpenWrt: Required dependency package kernel is not available in any repository.
by Nayla Nikolic 24 Feb '24

24 Feb '24

Hi I try to install podman on OpenWrt. Sadly there is no guide in official docs. Please update the docs. # Error Executing package manager Installing podman (4.8.0-1) to root... Downloading https://downloads.openwrt.org/releases/23.05.0/packages/aarch64_generic/pac… Errors Collected errors: * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.15.134-1-a61b316e83bc33130e55f5c8b8b65f74) for kmod-veth * pkg_hash_fetch_best_installation_candidate: Packages for kmod-veth found, but incompatible with the architectures configured * satisfy_dependencies_for: Cannot satisfy the following dependencies for podman: * kernel (= 5.15.134-1-a61b316e83bc33130e55f5c8b8b65f74) * opkg_install_cmd: Cannot install package podman. # Infos about my system: Model FriendlyElec NanoPi R4S Architecture ARMv8 Processor rev 4 Target Platform rockchip/armv8 Firmware Version OpenWrt 23.05.0 r23497-6637af95aa / LuCI openwrt-23.05 branch git-23.236.53405-fc638c8 Kernel Version 5.15.134 best regards Nayla

1 0

buildah push xxxxx docker-daemon:image:tag error
by Михаил Иванов 21 Feb '24

21 Feb '24

Hallo, When I try to push an image, created with buildah directly to docker, it aborts with following error: Error: pushing image "5d0da3dc9764" to "docker-daemon:test:2.0.0": writing blob: io: read/write on closed pipe No errors are logged by dockerdaemon. When I check what happens with strace, I see that it aborts on epoll_ctl error: epoll_ctl(4, EPOLL_CTL_ADD, 7, {events=EPOLLIN|EPOLLOUT|EPOLLRDHUP|EPOLLET, data={u32=4150263831, u64=9210128152865538071}}) = -1 EPERM 7 is file descriptor which refers to some file under /var/lib/containers (/var/lib/containers/storage/overlay-images/5d0da3dc976460b72c77d94c8a1ad043720b0416bfc16c52c45d4847e53fadb6/manifest) Is this supposed to work or do I misunderstand sthing? Best regards, -- Michael Ivanov

3 3

GPU devices in rootless
by lejeczek 20 Feb '24

20 Feb '24

Hi guys I have _rootless_ container with PyTorch from ROCm -> $ { export _NAME="pytorch_rocm"; export _PATH=${HOME}/containers/FLATfiles/${_NAME}; echo; mkdir -p ${_PATH}/{,root,dockerx}; }; podman run -dt --device=/dev/kfd --device=/dev/dri --group-add video --shm-size 8G --security-opt seccomp=unconfined --volume ${_PATH}/root:/root:z --volume ${_PATH}/dockerx:/dockerx:z -w /dockerx --name ${_NAME/\//_} rocm/pytorch:latest which fails to: root@4bc3c2ec2ab3:/dockerx# python3 -c 'import torch; print(torch.cuda.is_available())' False Such _rootful_ container seems a okey but rootless "suffers" such failures due to SELinux denials I think: ... SELinux is preventing /opt/conda/envs/py_3.9/bin/python3.9 from 'read, write' accesses on the chr_file kfd. For complete SELinux messages run: sealert -l 6b3db344-2ffc-4ecd-aa2c-2c1a2bfe23e4 SELinux is preventing /opt/conda/envs/py_3.9/bin/python3.9 from 'read, write' accesses on the chr_file kfd. Would you know if this can be fixed, possibly without building extra SE module(s)? many thanks, L.

3 3

ran out of storage - data lingers behind?
by lejeczek 20 Feb '24

20 Feb '24

Hi guys. Deploying a container I ran of local storage space & process failed - I see no new images nor container - yet disk space resulted being more occupied. I see _/var/lib/containers/storage/overlay_ being 21G large with, with my only freeIPA container makes little sense - there I looked first. How to clean such "unfortunate" case? many thanks, L.

3 2

Podman Community Cabal Mtg Tomorrow, Feb 20, 2024, at 11:00 a.m. EST (UTC-5)
by Tom Sweeney 19 Feb '24

19 Feb '24

Hi All, The next Podman Community Cabal meeting is happening tomorrow, Feb 20, 2024, at 11:00am EST (UTC-5). We will be talking about podman compose, image/container volumes, and Podman kube to handle VMs. Agenda with video link: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both Hope to see you there! t

1 0