- Podman - Podman List Archives

Error processing tar file(signal:killed)
by ugiwgh＠qq.com 07 Jul '22

07 Jul '22

When I pull an image, the image is 3.90GB, there is some error. Trying to pull xxx/xxx/xxx:xxx... Getting image source signatures Copying blob sha256:4184ac44fb0438b126437611d02f8ef889ad8a75ca91cd75b5b328d8e08cf66d Copying blob sha256:18fcb7509e4252365041f00982734e39ca0a44e638b8ebc18e2588405a5c7de2 Copying blob sha256:ea7643e57386e6b1e7b3524dd01d7e360b387ad640d32a7513ca263017175f87 Copying blob sha256:622a049262798701c22e70cb4e8ebff7e5dfb9c76d3dd948c49d5438ffe1e681 Copying blob sha256:d5fd17ec1767521cf97f61568096bfc9a7cd9c2d149576a7b43930c5a97062b0 Copying blob sha256:21e5db7c1fa24e99354f495e624cdc8920642b58ab65935db81bfceaf98a8a88 Copying blob sha256:ea7643e57386e6b1e7b3524dd01d7e360b387ad640d32a7513ca263017175f87 Copying blob sha256:18fcb7509e4252365041f00982734e39ca0a44e638b8ebc18e2588405a5c7de2 Copying blob sha256:d5fd17ec1767521cf97f61568096bfc9a7cd9c2d149576a7b43930c5a97062b0 Copying blob sha256:7240d5fd250b0bb7dbe6cad8d96e44e4548e895f9ca4f396275b7e0fab2dee35 Copying blob sha256:622a049262798701c22e70cb4e8ebff7e5dfb9c76d3dd948c49d5438ffe1e681 Copying blob sha256:4184ac44fb0438b126437611d02f8ef889ad8a75ca91cd75b5b328d8e08cf66d Copying blob sha256:21e5db7c1fa24e99354f495e624cdc8920642b58ab65935db81bfceaf98a8a88 Copying blob sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4 Copying blob sha256:7240d5fd250b0bb7dbe6cad8d96e44e4548e895f9ca4f396275b7e0fab2dee35 Copying blob sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4 Copying blob sha256:3343333b1de32753c9c373a8396895404bc7e8653594881d8242361ecc8ed091 Copying blob sha256:3343333b1de32753c9c373a8396895404bc7e8653594881d8242361ecc8ed091 Error: writing blob: adding layer with blob "sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4": Error processing tar file(signal: killed):

2 3

Looking for volunteers to write up documentation for Podman.
by Daniel Walsh 07 Jul '22

07 Jul '22

https://github.com/containers/podman/issues/13589 Might even be some bounty in it. Anyone interested?

1 0

strange network issue with npm
by Bjoern Franke 04 Jul '22

04 Jul '22

Hi, while running https://github.com/H2-invent/jitsi-admin/blob/master/installDocker.sh with podman (substituted docker-compose by podman-compose), npm install fails after some time. The corresponding Dockerfile is https://github.com/H2-invent/jitsi-admin/blob/master/Dockerfile npm timing metavuln:load:security-advisory:@holema/h2datetimepicker:tAOB5II05tSNmHF58Gp4WLe46M8ZRfnCB7f3pTeHPqNsrEBajJrlUdV7z6YjEmMaJ05Uih5vjS3zo1Lk7bPxCg== Completed in 0ms npm http fetch GET 200 https://registry.npmjs.org/@fullcalendar%2fmoment 1088ms (cache miss) npm timing metavuln:packument:@fullcalendar/moment Completed in 1088ms npm timing metavuln:load:security-advisory:@fullcalendar/moment:tAOB5II05tSNmHF58Gp4WLe46M8ZRfnCB7f3pTeHPqNsrEBajJrlUdV7z6YjEmMaJ05Uih5vjS3zo1Lk7bPxCg== Completed in 1ms npm timing reify:rollback:createSparse Completed in 834ms npm timing reify:rollback:retireShallow Completed in 0ms npm timing command:install Completed in 46331ms npm notice npm notice New minor version of npm available! 8.3.1 -> 8.13.2 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.13.2> npm notice Run `npm install -g npm(a)8.13.2` to update! npm notice npm verb stack Error: Socket timeout npm verb stack at TLSSocket.onTimeout (/usr/lib/node_modules/npm/node_modules/agentkeepalive/lib/agent.js:346:23) npm verb stack at TLSSocket.emit (node:events:402:35) npm verb stack at TLSSocket.Socket._onTimeout (node:net:501:8) npm verb stack at listOnTimeout (node:internal/timers:557:17 The issue does not appear with docker, and the container can connect outside, otherwise the 200s before wouldn't happen. I'm confused where the timeout comes from. Best Regards Bjoern

1 0

Why does Podman update the "Change" timestamp on files shared between host and guest ?
by Jacob Kroon 29 Jun '22

29 Jun '22

Hi, I'm using Podman in my build environment. As part of the build I bind a directory from the host to a directory in the container. Even though the guest doesn't touch the file in any way, afterwards I can see that the file's "Change" timestamp has been updated, so I am assuming it is podman that does this. According to https://unix.stackexchange.com/questions/2464/timestamp-modification-time-a… the "Change" timestamp is described as "the last time meta data of the file was changed (e.g. permissions)". I am wondering what meta data it is that podman changes, and if it can be avoided somehow ? (Mainly because it tricks git/gitk into thinking something might have changed). Regards Jacob

2 10

IPv6 only listener in rootless container
by Hendrik Haddorp 23 Jun '22

23 Jun '22

Hi, I created a container that contains a service that is only listening for tcp6 requests, so is IPv6 only. When starting the container rootless on Fedora 36 with podman 4.1.0 I'm unable to connect to my service. However when I start my service to listen just for tcp4 requests I can connect to it using IPv4 and IPv6. So it looks like the port forwarding done by podman always forwards the traffic as IPv4. Is that the correct? I could not find any documentation on that. The problem looks however a bit like https://github.com/containers/podman/issues/14491. That issue states that there is a proxy (rootlessport) running that does the forwarding. Are there more details available how this is done exactly? Ideally I would like to be able to start a service that uses just tcp4 or tcp6 to only be accessible via tcp4 or tcp6. Podman should simply keep the protocol when forwarding traffic and not translate it. regards, Hendrik

2 1

Run VASP with Podman
by ugiwgh＠qq.com 23 Jun '22

23 Jun '22

When I run hello_c, it runs success. But vasp_std runs failed. When I run vasp_std on host(mpirun -np 20 ./vasp_std), it runs success. $ podman run --env-host --env-file envfile --userns=keep-id --network=host --pid=host --ipc=host -v /tmp/podman-mpirun:/tmp/podman-mpirun:z -v ./bulk:/bulk -w /bulk 4756bc6d2be0 mpirun -np 20 ./hello_c Hello, world, I am 13 of 20, (Open MPI v4.1.1, package: Open MPI root@6831ad9910ad Distribution, ident: 4.1.1, repo rev: v4.1.1, Apr 24, 2021, 112) Hello, world, I am 16 of 20, (Open MPI v4.1.1, package: Open MPI root@6831ad9910ad Distribution, ident: 4.1.1, repo rev: v4.1.1, Apr 24, 2021, 112) ... ... ... ... Hello, world, I am 9 of 20, (Open MPI v4.1.1, package: Open MPI root@6831ad9910ad Distribution, ident: 4.1.1, repo rev: v4.1.1, Apr 24, 2021, 112) $ podman run --env-host --env-file envfile --userns=keep-id --network=host --pid=host --ipc=host -v /tmp/podman-mpirun:/tmp/podman-mpirun:z -v ./bulk:/bulk -w /bulk 4756bc6d2be0 mpirun -np 20 ./vasp_std running on 20 total cores distrk: each k-point on 20 cores, 1 groups ... ... ... ... LDA part: xc-table for Pade appr. of Perdew POSCAR, INCAR and KPOINTS ok, starting setup [ga2210.para.bscc:106293] Read -1, expected 5184, errno = 1 [ga2210.para.bscc:106294] Read -1, expected 5184, errno = 1 [ga2210.para.bscc:106296] Read -1, expected 5184, errno = 1 [ga2210.para.bscc:106300] Read -1, expected 5184, errno = 1 [ga2210.para.bscc:106309] Read -1, expected 5184, errno = 1 ... ... ... ... VASP version: vasp.5.4.4.18Apr17-6-g9f103f2a3. OpenMPI version: 4.1.1 $ podman version Client: Podman Engine Version: 4.0.2 API Version: 4.0.2 Go Version: go1.16.13 Git Commit: c99f9f1b6960b98158b7f5fc4e6b5ac1a10b3542 Built: Wed Mar 23 18:33:41 2022 OS/Arch: linux/amd64

1 1

cgroups not configured for container
by ugiwgh＠qq.com 23 Jun '22

23 Jun '22

There is somthing warning, when I add "--pid=host". How can I get this warning gone? OS: 8.3.2011 Podman: 2.2.1 [rsync@rsyncdk2 ~]$ podman run --rm --pid=host fb7ad16314ee sleep 3 WARN[0000] cannot toggle freezer: cgroups not configured for container WARN[0000] lstat : no such file or directory

2 2

Run OpenMPI with Podman
by ugiwgh＠qq.com 23 Jun '22

23 Jun '22

I have set "btl_tcp_if_include = ib0" in ~/.openmpi/mca-params.conf. When I run mpirun without podman, it runs right. When I run mpirun with podman, the "btl_tcp_if_include = ib0" is invalid. But when I add "--mca btl_tcp_if_include ib0" to command line, it is valid. $ mpirun -np 128 --hostfile mfile --mca btl_vader_single_copy_mechanism 3 --mca orte_tmpdir_base /tmp/podman-mpirun podman run --env-host --env-file envfile --userns=keep-id --network=host --pid=host --ipc=host -v /tmp/podman-mpirun:/tmp/podman-mpirun:z -v ./bulk:/bulk -w /bulk 4756bc6d2be0 vasp_std running on 128 total cores [ga2211][[19883,1],64][btl_tcp_endpoint.c:626:mca_btl_tcp_endpoint_recv_connect_ack] received unexpected process identifier [[19883,1],88] ... ... Here is hang. ... ... VASP version: vasp.5.4.4.18Apr17-6-g9f103f2a3. OpenMPI version: 4.1.1 $ podman version Client: Podman Engine Version: 4.0.2 API Version: 4.0.2 Go Version: go1.16.13 Git Commit: c99f9f1b6960b98158b7f5fc4e6b5ac1a10b3542 Built: Wed Mar 23 18:33:41 2022 OS/Arch: linux/amd64

2 2

Invitation to discussion: Is Podman for Linux workstations like Podman for servers or like podman for Windows WSL and Mac?
by Pavel Sosin 21 Jun '22

21 Jun '22

Podman doesn't work on Fedora Workstations with GNome-basedGUI. It's a fact. But How OCI container's cgroups soft machine can work in the forest of cgroups created by GNome and all GUI applications. Every GUI session has its own cgroups tree managed by systemd. It is very hard to make a decision about a parent cgroup for the created container and resource allocation that doesn't fit every scenario. There are too many variants: user-session, gnome-terminal, gnome-terminal tab, etc. The server-client nature of the Gnome GUI will keep the question about a side designated for resource allocation forever. The Windows WSL and MAC implementation of Podman follo different approach - creation of the singleton VM running pre-installed Podman. Fedora workstations have built-in capability to run VMs via machined and machinectl. The resource limits of this VM can be easily tuned. Inside the VM OCI containers can be easily managed if the VM is systemd-based like Fedora's images. User sessions in this VM are plain remote sessions opened by the user core or core-less. Such VM can be easily deployed to Fedora WS as a iso copied to btrfs volume. I tried to run minimalistic smoke-test and got a workable Podman but the Quemi machine inside Fedora WS for Intel looks slightly exotic. Maybe this approach is more practical?

3 2

podman intel mpi container
by ugiwgh＠qq.com 17 Jun '22

17 Jun '22

I run podman with intel mpi. But there is something wrong. Any help will be appreciated. --GHui $ mpirun --version Intel(R) MPI Library for Linux* OS, Version 2021.5 Build 20211102 (id: 9279b7d62) Copyright 2003-2021, Intel Corporation. $ mpirun -np 2 podman run --env-host --env-file envfile --network=host --pid=host --ipc=host -w /exports -v .:/exports:z centos/ /exports/mpitest [cli_0]: write_line error; fd=9 buf=:cmd=init pmi_version=1 pmi_subversion=1 : system msg for write_line failure : Bad file descriptor [cli_0]: Unable to write to PMI_fd [cli_0]: write_line error; fd=9 buf=:cmd=get_appnum : system msg for write_line failure : Bad file descriptor Abort(1090575) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack: MPIR_Init_thread(143): MPID_Init(1221)......: MPIR_pmi_init(130)...: PMI_Get_appnum returned -1 [cli_0]: write_line error; fd=9 buf=:cmd=abort exitcode=1090575 : system msg for write_line failure : Bad file descriptor Attempting to use an MPI routine before initializing MPICH [cli_1]: write_line error; fd=10 buf=:cmd=init pmi_version=1 pmi_subversion=1 : system msg for write_line failure : Bad file descriptor [cli_1]: Unable to write to PMI_fd [cli_1]: write_line error; fd=10 buf=:cmd=get_appnum : system msg for write_line failure : Bad file descriptor Abort(1090575) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack: MPIR_Init_thread(143): MPID_Init(1221)......: MPIR_pmi_init(130)...: PMI_Get_appnum returned -1 [cli_1]: write_line error; fd=10 buf=:cmd=abort exitcode=1090575 : system msg for write_line failure : Bad file descriptor Attempting to use an MPI routine before initializing MPICH ^C[mpiexec(a)ja0909.para.bscc] Sending Ctrl-C to processes as requested [mpiexec(a)ja0909.para.bscc] Press Ctrl-C again to force abort

3 5