March 2023 - Podman - Podman List Archives

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

mqueue msg_max in rootless container
by Michael Ivanov 27 Nov '23

27 Nov '23

Hallo! I'm trying to run my application in podman rootless container and I stumble on following problem: my program needs /proc/sys/fs/mqueue/msg_max to be at least 256, but in running container this value is just 10. When I try to specify this parameter while running the image (--sysctl 'fs.mqueue.msg_max=256') I get the following error: Error: open /proc/sys/fs/mqueue/msg_max: Permission denied: OCI permission denied and container is not created. My host where container is being run has this parameter set to 256. How can I expose current host setting for msg_max to my container? Best regards, -- \ / | | (OvO) | Михаил Иванов | (^^^) | | \^/ | E-mail: ivans(a)isle.spb.ru | ^ ^ | |

4 10

Containers Plumbing Days Starts Wednesday March 22, 2023!
by Tom Sweeney 20 Mar '23

20 Mar '23

Containers Plumbing Days kicks off the day after tomorrow! Free to attend the virtual conference. - Date: March 22-23, 13:00 UTC to 18:00 UTC (9:00 to 15:00 EDT UTC-5). - Schedule: https://containerplumbing.org/schedule - Registration is still open (and free!): https://containerplumbing.org/register Hope to see you there! t

1 0

Podman Community Cabal Meeting, Thu March 16, 2023, 11:00 a.m. EDT (UTC-5)
by Tom Sweeney 15 Mar '23

15 Mar '23

Hi All, The Podman Community Cabal meeting is happening in just over 21 hours tomorrow, Thursday, March 16, 2023, at 11:00 am EDT (UTC-5). We'll be talking about SQLite in Podman, Perf Scripts, and Test Days. Agenda with video link: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both Note that the US has gone to Daylight savings, but Europe hasn't. Hope to see you there! t

1 0

Container Plumbing Days 2023 happening a week from Wednesday
by Tom Sweeney 14 Mar '23

14 Mar '23

Containers Plumbing Days 2023 kicks off one week from Wednesday! Free to attend the virtual conference. - Date: Wed/Thu March 22-23, 13:00 UTC to 18:00 UTC (9:00 to 15:00 EDT UTC-5). * Schedule: https://containerplumbing.org/schedule * Registration is open: https://containerplumbing.org/register Hope to see you there! t

1 0

passt (pasta(1)) package to be included in Fedora CoreOS 37/38
by Stefano Brivio 09 Mar '23

09 Mar '23

Hi Podman team, For your awareness: Fedora CoreOS is going to include the passt package (providing the 'pasta' network back-end): https://github.com/coreos/fedora-coreos-tracker/issues/1436 https://meetbot.fedoraproject.org/fedora-meeting-1/2023-03-08/fedora_coreos… Hence Podman users on Fedora CoreOS will be able to use it soon. Let me know if there are any questions or concerns. Thanks! -- Stefano

3 8

lsetxattr /dev/initctl: operation not permitted
by GHui Wu 03 Mar '23

03 Mar '23

When I pull mysql, there is error "lsetxattr /dev/initctl: operation not permitted". But I pull centos successfully. $ podman pull docker.io/library/mysql:8.0.30 Trying to pull docker.io/library/mysql:8.0.30... Getting image source signatures Copying blob 48d3d73d1704 done Copying blob b8cf360b4a14 done Copying blob 295ca2342728 done Copying blob 79af4312a7e0 done Copying blob 0115482cc006 done Copying blob 521b8724b397 done Copying blob a360b08917ea done Copying blob 12deeb3c1323 done Copying blob ee1dc10db1e9 done Copying blob 64be404ad29c done Copying blob 1921fe8879a2 done Error: writing blob: adding layer with blob "sha256:295ca23427284cb123fd4c132a1ecb521e7f787ac75dadec342f744a343efec4": Error processing tar file(exit status 1): lsetxattr /dev/initctl: operation not permitted $ podman pull docker.io/library/centos Trying to pull docker.io/library/centos:latest... Getting image source signatures Copying blob a1d0c7532777 done Copying config 5d0da3dc97 done Writing manifest to image destination Storing signatures 5d0da3dc976460b72c77d94c8a1ad043720b0416bfc16c52c45d4847e53fadb6

3 4