January 2023 - Podman - Podman List Archives

shouldn't the current directory be the default context for "podman build"?

by Robert P. J. Day

"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

2 months, 2 weeks

4
5
0 / 0

mqueue msg_max in rootless container

by Michael Ivanov

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 | ^ ^ | |

1 year, 3 months

4
10
0 / 0

What is rundir?

by GHui Wu

When I pull an image, there is an error. Login Succeeded! Trying to pull xxx.com/name:7.0... Getting image source signatures Copying blob sha256:b294330b903102b99b9272e8c639135e74bc7935a32d0b8a06443b86779ed546 Copying blob sha256:e5a33881590f6c79e508c14a7a529207fbb473d352ff3ea6f02c5cc8c685502f Copying blob sha256:d9ba75c043daa80149b5d7bfe3a8732ea56ea5f7bf7e6baf50f213352dde872f Copying config sha256:093e23f8df9aa2891b3e87581b2fc136569db41ef01617b0c35a13bafb6a1c20 Writing manifest to image destination Storing signatures 093e23f8df9aa2891b3e87581b2fc136569db41ef01617b0c35a13bafb6a1c20 093e23f8df9aa2891b3e87581b2fc136569db41ef01617b0c35a13bafb6a1c20 Error: chown /home/myuser/rundir/containers/overlay-containers/6c47fca6915e0e1491b1f29e3e4e1e1dd6b53620591ff65d9cc61094fc4912e0/userdata: operation not permitted

2 years

2
3
0 / 0

Podman desktop connection error

by LINZ, Arnaud

Hello, I've tried to install podman on my Windows 10 system, and had a hard time with it (make it compatible with VPN, proxies, etc.) I've managed to make podman works in command line. I can pull image, run containers, everything is fine. I can ssh in the podman machine just fine too. However, I'm unable to make podman desktop work. I've uninstalled and reinstalled it several times already. The only things the desktop can do is to start/stop podman, but every time pdoman desktop needs to communicate with podman (get images, pull images, etc.), I have nodejs uncaught exceptions popups showing that "All configured authentication methods failed" (app.asar/node_m... at Socket.emit) I've searched the internet for some explanation, or simply to find a detailed log location, with no success. How can I fix this error please? How can I configure the way podman desktop communicates with podman? Where are the logs? Thanks, Arnaud ________________________________ L'int?grit? de ce message n'?tant pas assur?e sur internet, la soci?t? exp?ditrice ne peut ?tre tenue responsable de son contenu ni de ses pi?ces jointes. Toute utilisation ou diffusion non autoris?e est interdite. Si vous n'?tes pas destinataire de ce message, merci de le d?truire et d'avertir l'exp?diteur. The integrity of this message cannot be guaranteed on the Internet. The company that sent this message cannot therefore be held liable for its content nor attachments. Any unauthorized use or dissemination is prohibited. If you are not the intended recipient of this message, then please delete it and notify the sender.

2 years

1
0
0 / 0

Rootless storage usage

by Михаил Иванов

Hallo, I notice some disk space discrepancy when running rootless podman containers. I use dedicated fs for podman storage mountrd to ~/.local/share/containers. df and du show consistent used disk space: island:named [master]> df -h ~/.local/share/containers /dev/mapper/sys-containers 117G 84G 32G 73% ~/.local/share/containers island:named [master]> sudo du -sh ~/.local/share/containers/storage/{vfs,volumes} 74G /home/ivans/.local/share/containers/storage/vfs 11G /home/ivans/.local/share/containers/storage/volumes island:named [master]> But space usage shown by podman system df is about 44% less than reported above: island:named [master]> podman system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 32 5 39.49GB 25.96GB (66%) Containers 7 7 1.85GB 0B (0%) Local Volumes 2 2 10.83GB 0B (0%) Volume space is practically same, it's vfs space (where as I understand images and containers are located) that differs. I also run buildah as same user, but buildah ls shows nothing. I have ran podman system prune, but it reclaimed 0 bytes. So is this extra space usage expected? Or is it sthing wrong with my storage? Thanks and regards, -- Michael Ivanov

2 years, 1 month

4
19
0 / 0

podman systemd file for mssql-server

by mwindham＠troglobytor.com

I did another generate today and after some tinkering with options got the below, and I don't have a clue what went wrong in original post. sudo podman generate systemd -n -f --restart-policy=always sqlx22 >pdm2sysd.txtsudo cp container-sqlx22.service /etc/systemd/system sudo systemctl enable container-sqlx22.service works # container-sqlx22.service # autogenerated by Podman 4.2.0 # Tue Jan 24 17:00:30 CST 2023 [Unit] Description=Podman container-sqlx22.service Documentation=man:podman-generate-systemd(1) Wants=network-online.target After=network-online.target RequiresMountsFor=/run/containers/storage [Service] Environment=PODMAN_SYSTEMD_UNIT=%n Restart=always TimeoutStopSec=70 ExecStart=/usr/bin/podman start sqlx22 ExecStop=/usr/bin/podman stop -t 10 sqlx22 ExecStopPost=/usr/bin/podman stop -t 10 sqlx22 PIDFile=/run/containers/storage/overlay-containers/afcbd216eedb0d74075a522e8 fc6cfc5a8dc8a0a3dfb2ce65434891b30fb0eb8/userdata/conmon.pid Type=forking [Install] WantedBy=default.target

2 years, 1 month

1
0
0 / 0

podman systemd file for mssql-server

by mwindham＠troglobytor.com

I used "podman generate systemd" for a configured sqlx22 named container and got the attached file which seems to have all the initial configuration command. What would be the minimal revised ExecStart to use after configuration? Do I need to keep specifying name and hostname? I would think all the -e 's should be omitted? When I start from command line all I use is "sudo podman start sqlx22". podman generated ExecStart: ExecStart=/usr/bin/podman run \ --cidfile=%t/%n.ctr-id \ --cgroups=no-conmon \ --rm \ --sdnotify=conmon \ --replace \ -e ACCEPT_EULA=Y \ -e MSSQL_SA_PASSWORD=SQueeZY2*ZX \ -e MSSQL_PID=Express \ --name sqlx22 \ --hostname sqlx22 \ -p 1433:1433 \ -d mcr.microsoft.com/mssql/rhel/server:2022-latest

2 years, 1 month

1
0
0 / 0

Container restart issue: Failed to attach 1 to compat systemd cgroup

by Lewis Gaul

Hi Podman team, I came across an unexpected systemd warning when running inside a container - I emailed systemd-devel (this email summarises the thread, which you can find at https://lists.freedesktop.org/archives/systemd-devel/2023-January/048723....) and Lennart suggested emailing here. Any thoughts would be great! There are two different warnings seen in different scenarios, both cgroups related, and I believe related to each other given they both satisfy the points below. The first warning is seen after 'podman restart $CTR', coming from https://github.com/systemd/systemd/blob/v245/src/shared/cgroup-setup.c#L279: Failed to attach 1 to compat systemd cgroup /machine.slice/libpod-5e4ab2a36681c092f4ef937cf03b25a8d3d7b2fa530559bf4dac4079c84d0313.scope/init.scope: No such file or directory The second warning is seen on every boot when using '--cgroupns=private', coming from https://github.com/systemd/systemd/blob/v245/src/core/cgroup.c#L2967: Couldn't move remaining userspace processes, ignoring: Input/output error Failed to create compat systemd cgroup /system.slice: No such file or directory ... Both warnings are seen together when restarting a container using private cgroup namespace. To summarise: - The warnings are seen when running the container on a Centos 8 host, but not on an Ubuntu 20.04 host - It is assumed this issue is specific to cgroups v1, based on the warning messages - Disabling SELinux on the host with 'setenforce 0' makes no difference - Seen with systemd v245 but not with v230 - Seen with '--privileged' and in non-privileged with '--cap-add sys_admin' - Changing the cgroup driver/manager doesn't seem to have any effect - The same is seen with docker except when running privileged the first warning becomes a fatal error after hitting "Failed to open pin file: No such file or directory" (coming from https://github.com/systemd/systemd/blob/v245/src/core/cgroup.c#L2972) and the container exits (however docker doesn't claim to support systemd) Some extra details copied from the systemd email thread: - On first boot PID 1 can be found in /sys/fs/cgroup/systemd/machine.slice/libpod-<ctr-id>.scope/init.scope/cgroup.procs, whereas when the container restarts the 'init.scope/' directory does not exist and PID 1 is instead found in the parent (container root) cgroup /sys/fs/cgroup/systemd/machine.slice/libpod-<ctr-id>.scope/cgroup.procs (also reflected by /proc/1/cgroup). This is strange because systemd must be the one to create this cgroup dir in the initial boot, so I'm not sure why it wouldn't on subsequent boot. - I confirmed that the container has permissions to create the dir by executing a 'mkdir' in /sys/fs/cgroup/systemd/machine.slice/libpod-<ctr-id>.scope/ inside the container after the restart, so I have no idea why systemd is not creating the 'init.scope/' dir. I notice that inside the container's systemd cgroup mount 'system.slice/' does exist, but 'user.slice/' also does not (both exist on normal boot). This should be reproducible using the following: cat << EOF > Dockerfile FROM ubuntu:20.04 RUN apt-get update -y && apt-get install systemd -y && ln -s /lib/systemd/systemd /sbin/init ENTRYPOINT ["/sbin/init"] EOF podman build . --tag ubuntu-systemd podman run -it --name ubuntu --privileged --cgroupns private ubuntu-systemd podman restart ubuntu Thanks, Lewis

2 years, 1 month

2
1
0 / 0

Podman Community Cabal Meeting - Thursday January 19, 2023, 11:00 a.m. EST (UTC-5)

by Tom Sweeney

Hi All, The next Podman Community Cabal meeting is happening in just under 20 hours from now, at 11:00am EST (UTC-5). We'll be talking about Podman v4.4, auto-closing issues, and more! Agenda with video conference link: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both <https://t.co/sYgIaGn8rS> Hope to see you there! t

2 years, 1 month

1
0
0 / 0

bolt_state.db: no such file or directory

by GHui Wu

I run "podman run --rm xxxx". When the container runs completely, there output the following error. Could not retrieve exit code: error opening database /tmp/3199/19531/share/containers/storage/libpod/bolt_state.db: open /tmp/3199/19531/share/containers/storage/libpod/bolt_state.db: no such file or directory I have checked the /tmp/3199/19531/share/containers/storage, there is no such directory.

2 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

Podman January 2023