- Podman - Podman List Archives

Shipping Podman RCs in Distros
by Lokesh Mandvekar 13 Feb '23

13 Feb '23

Hi all, Opening up an earlier rather private discussion RE: "Fedora and upstream RC releases" to get feedback from the community, especially distro users / maintainers other than Fedora / CentOS, including maintainers of homebrew, snap, etc. Podman upstream usually releases RCs before any minor version bump, and there's approximately a month between the first RC and the .0 release. Now Fedora has a policy of consumable updates which says any build that gets submitted to the testing repos should be good enough for the stable repos. Ref: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#consumable-updat… Currently, Podman RCs aren't always a 100% release-worthy which means Fedora can't ship an RC build even to its testing repos and that means a month's worth of community testing lost. Similar situation with CentOS Stream. So, here's what I'm hoping to know: 1. Do other distros ship Podman RCs soon as they are available or do you wait until the final release? 2. Would it be easier for distros to ship RCs if upstream ensured every RC is good enough to be released or does the "RC" in the tag itself scare users away? In which case we could perhaps do away with RC tagging. Thanks, -- Lokesh Libera, GitLab, GitHub, Fedora: lsm5 Matrix: @lsm5:lsm5.ems.host GPG: 0xC7C3A0DD https://keybase.io/lsm5

1 0

Use host proxy inside container
by Mehdi Haghgoo 08 Feb '23

08 Feb '23

Hello, I need to use a network proxy running with socks as socks5://127.0.0.1:1090 on my host system, inside the container running with podman. How can I tell Podman to use that proxy inside the container as well?Does Podman support this?

2 3

Podman Community Meeting Tuesday, February 7, 2023 at 11:00 a.m. EST (UTC-5)
by Tom Sweeney 06 Feb '23

06 Feb '23

Hi All, The Podman Community Meeting is happening just over 20 hours from now, at 11:00 am EST (UTC-5) tomorrow, Feb 7, 2023. There'll be a demo on Pasta in Podman and updates on Podman v4.4 and Desktop. Video link in the Agenda, hope to see you there! https://podman.io/community/meeting/agenda/ t

1 0

Will there be a Podman extension for VS Code?
by Mehdi Haghgoo 06 Feb '23

06 Feb '23

Hi, Will there ever be a Docker-Desktop-compatible Podman extension for VS Code? I think it is very much needed, especially on Windows.

3 3

rootless buildah in toolbox container
by Hendrik Haddorp 04 Feb '23

04 Feb '23

Hi, I want to create a custom toolbox (https://github.com/containers/toolbox) image and use rootless buildah inside the container created by toolbox on Fedora. Are there any instructions on that? Or maybe an example? thanks, Hendrik

3 4

Reliable service starts
by Mark Raynsford 03 Feb '23

03 Feb '23

Hello! I'm using podman on Fedora CoreOS. The standard setup for a podman-based service tends to look like this (according to the documentation): --- [Unit] Description=looseleaf After=network-online.target Wants=network-online.target [Service] Type=exec TimeoutStartSec=60 User=_looseleaf Group=_looseleaf Restart=on-failure RestartSec=10s Environment="_JAVA_OPTIONS=-XX:+UseSerialGC -Xmx64m -Xms64m" ExecStartPre=-/bin/podman kill looseleaf ExecStartPre=-/bin/podman rm looseleaf ExecStartPre=/bin/podman pull docker.io/io7m/looseleaf:0.0.4 ExecStart=/bin/podman run \ --name looseleaf \ --volume /var/storage/looseleaf/etc:/looseleaf/etc:Z,ro \ --volume /var/storage/looseleaf/var:/looseleaf/var:Z,rw \ --publish 20000:20000/tcp \ --memory=128m \ --memory-reservation=80m \ docker.io/io7m/looseleaf:{{looseleaf_version}} \ /looseleaf/bin/looseleaf server --file /looseleaf/etc/config.json ExecStop=/bin/podman stop looseleaf [Install] WantedBy=multi-user.target --- The important line is this one: /bin/podman pull docker.io/io7m/looseleaf:0.0.4 Unfortunately, this line can fail. That in itself isn't a problem, the service will be restarted and it'll run again. The real problem is that it can fail in ways that will break all subsequent executions. On new Fedora CoreOS deployments, there's often a lot of network traffic happening on first boot as the rest of the system updates itself, and it's not unusual for `podman pull` to fail and leave the services permanently broken (unless someone goes in and fixes them). This is what will typically happen: Feb 02 20:31:05 control1.io7m.com podman[1934]: Trying to pull docker.io/io7m/looseleaf:0.0.4... Feb 02 20:31:48 control1.io7m.com podman[1934]: time="2023-02-02T20:31:48Z" level=warning msg="Failed, retrying in 1s ... (1/3). Error: initializing source docker://io7m/looseleaf:0.0.4: pinging container registry registry-1.docker.io: Get \"https://regist> Feb 02 20:31:50 control1.io7m.com podman[1934]: Getting image source signatures Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob sha256:9794579c486abc6811cea048073584c869db02a4d9b615eeaa1d29e9c75738b9 Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob sha256:8921db27df2831fa6eaa85321205a2470c669b855f3ec95d5a3c2b46de0442c9 Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob sha256:846e3b32ee5a149e3ccb99051cdb52e96e11488293cdf72ee88168c88dd335c7 Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob sha256:7f516ed68e97f9655d26ae3312c2aeede3dfda2dd3d19d2f9c9c118027543e87 Feb 02 20:31:50 control1.io7m.com podman[1934]: Copying blob sha256:e88daf71a034bed777eda8657762faad07639a9e27c7afb719b9a117946d1b8a Feb 02 20:32:03 control1.io7m.com systemd[1]: looseleaf.service: start-pre operation timed out. Terminating. It'll usually happen again on the next service restart. Then, this will tend to happen: Feb 02 20:34:13 control1.io7m.com podman[2745]: time="2023-02-02T20:34:13Z" level=error msg="Image docker.io/io7m/looseleaf:0.0.4 exists in local storage but may be corrupted (remove the image to resolve the issue): size for layer \"13cfed814d5b083572142bc> Feb 02 20:34:13 control1.io7m.com podman[2745]: Trying to pull docker.io/io7m/looseleaf:0.0.4... Feb 02 20:34:14 control1.io7m.com podman[2745]: Getting image source signatures Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob sha256:9794579c486abc6811cea048073584c869db02a4d9b615eeaa1d29e9c75738b9 Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob sha256:8921db27df2831fa6eaa85321205a2470c669b855f3ec95d5a3c2b46de0442c9 Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob sha256:846e3b32ee5a149e3ccb99051cdb52e96e11488293cdf72ee88168c88dd335c7 Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob sha256:7f516ed68e97f9655d26ae3312c2aeede3dfda2dd3d19d2f9c9c118027543e87 Feb 02 20:34:14 control1.io7m.com podman[2745]: Copying blob sha256:e88daf71a034bed777eda8657762faad07639a9e27c7afb719b9a117946d1b8a Feb 02 20:34:18 control1.io7m.com podman[2745]: Copying config sha256:cce9701f3b6e34e3fc26332da58edcba85bbf4f625bdb5f508805d2fa5e62e3e Feb 02 20:34:18 control1.io7m.com podman[2745]: Writing manifest to image destination Feb 02 20:34:18 control1.io7m.com podman[2745]: Storing signatures Feb 02 20:34:18 control1.io7m.com podman[2745]: Error: checking platform of image cce9701f3b6e34e3fc26332da58edcba85bbf4f625bdb5f508805d2fa5e62e3e: inspecting image: size for layer "13cfed814d5b083572142bc068ae7f890f323258135f0cffe87b04cb62c3742e" is unkno> Feb 02 20:34:18 control1.io7m.com systemd[1]: looseleaf.service: Control process exited, code=exited, status=125/n/a At this point, there's really nothing that can be done aside from having a human log in and running something like "podman system reset". These systems are supposed to be as immutable as possible, and deployments are supposed to be automated. As it stands currently, I can't actually a deploy a machine and not have it immediately break and require a manual intervention. Is there some better way to handle this? -- Mark Raynsford | https://www.io7m.com

3 4

I am not able to install gpgme on RHEL 9
by adhish meena 02 Feb '23

02 Feb '23

Hi team, Currently I am using RHEL 9. I have been trying to setup dev env of podman on my pc but I am not able to install gpgme-devel. could you please suggest how shall I resolve this? Regards Adhish Meena

2 1

How does podman auto create runRoot directory
by GHui Wu 02 Feb '23

02 Feb '23

I have set XDG_RUNTIME_DIR as following. export XDG_RUNTIME_DIR=/.sllocal/log/containers-user-$UID/containers But when I execute "podman info", there output error. $ podman info ERRO[0000] stat /.sllocal/log/containers-user-3088/containers: no such file or directory How does podman auto create runRoot directory?

2 4

Podman desktop connection error
by LINZ, Arnaud 30 Jan '23

30 Jan '23

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.

1 0

Rootless storage usage
by Михаил Иванов 25 Jan '23

25 Jan '23

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

4 19