- Podman - Podman List Archives

--dns=ipaddr - no effect of it
by lejeczek 30 May '23

30 May '23

Hi guys. --dns=none renders what expected but with an actual server, say: --dns=10.3.1.200 resolve.conf seems to be the one of the host's, as if --dns did not happen. Can anybody else say that is the case? Am I missing something? I'm on Centos 9 stream with all bits up-to-date. many thanks, L.

3 6

Podman Desktop unable to setup Docker Compose
by Mehdi Haghgoo 27 May '23

27 May '23

Hi, On mac, I can simply press the Compose hint on the status bar for Podman Desktop and it sets up docker-compose. On Linux, however, when I press the hint, I get the following error: "Please add the compose wrapper bin folder to your PATH environment variable. Value is /home/mehdi/.local/share/containers/podman-desktop/extensions-storage/compose/bin. The script /home/mehdi/.local/share/containers/podman-desktop/extensions-storage/compose/bin/compose will setup for you the DOCKER_HOST environment variable." I tried adding the mentioned value to the PATH in ~/.bash_profile and logging out and logging in, but it does not work. I always get the same error. Looks like I can directly run "/home/mehdi/.local/share/containers/podman-desktop/extensions-storage/compose/bin/compose up" to start a compose project, which is interesting. Or, I might be able to go the manual way (as before) of setting DOCKER_HOST to point to the Podman socket, but why doesn't the Podman Desktop way not work? Am I doing something wrong? Mehdi/

2 1

Podman Community Meeting - Tuesday, June 6, 2023, 11:00 a.m. EDT (UTC-5)
by Tom Sweeney 23 May '23

23 May '23

Hi All! The next Podman Community Meeting is just 13 days, 21 hours, and a few minutes from now! We'll be talking about the ChRIS project's use of Podman, Podman v4.5, a Qudadlet demo, and Podman Desktop v1.0. Agenda with video link: https://hackmd.io/fc1zraYdS0-klJ2KJcfC7w #opensource #podman Hope to see you there! t

1 0

How does podman set rootfs ownership to root when using --userns keep-id ?
by Fabio 22 May '23

22 May '23

Hi all, I'm trying to understand some of the internals of namespace-based Linux containers and I'm kindly asking you for help. When launching `podman run -it --rm -v ~/Downloads:/dwn docker.io/library/ubuntu /bin/bash`, the inside user is root. That is expected, and without any surprise the /proc/self/uid_map is: 0 1000 1 1 100000 65536 When launching `podman run -it --rm -v ~/Downloads:/dwn --userns keep-id docker.io/library/ubuntu /bin/bash` instead, the /proc/self/uid_map is: 0 1 1000 1000 0 1 1001 1001 64536 If I'm understanding it well, in the latter case there is a double mapping: to keep host UID and GID, podman fires two user namespaces, where the inner namespace maps its IDs the outer namespace, which finally maps to the host (that is, 1000 -> 0 -> 1000 again). The mechanism I don't get is how podman manages to make the rootfs owned by root inside the inner namespace, while assigning volumes to the unprivileged inner user: dr-xr-xr-x. 1 root root 18 May 4 06:33 . dr-xr-xr-x. 1 root root 18 May 4 06:33 .. lrwxrwxrwx. 1 root root 7 Mar 8 02:05 bin -> usr/bin drwxr-xr-x. 1 root root 0 Apr 18 2022 boot [...] drwxr-xr-x. 1 myuser 1000 2.1K May 3 15:07 dwn What is the algorithm here? I have a feeling there is some clever combination of syscalls here I don't get. When I tried to reproduce this double namespace situation, the rootfs of the inner namespace was all owned by 1000, not 0. Thank you so so much for your time if you're willing to help me, Fabio.

3 3

Podman Community Cabal Meeting - Thur May 18, 2023, 11:00 a.m. EDT (UTC-5)
by Tom Sweeney 17 May '23

17 May '23

Hi All, A quick reminder that the Podman Cabal meeting will be happening in just under 24 hours from now, at 11:00am EDT (UTC-5) on Thu May 19. We will be talking about Storage layers, containersh, http://podman.io <https://t.co/R5FbTKrfcV>revamp, and the Containers AppStore. Agenda w/ conference link: https://hackmd.io/gQCfskDuRLm7iO <https://t.co/sYgIaGmACk> Hope to see you there! t

1 1

Podman Community Cabal Meeting, Thur, May 18, 2023, at 11:00 am EDT (UTC-5)
by Tom Sweeney 11 May '23

11 May '23

Hi All, The next Podman Community Cabal Meeting is happening a week from now, on Thur, May 18, 2023, at 11:00 am EDT (UTC-5). We'll be talking containers, splitting storage layers, and more! Agenda with video conference link: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg Hope to see you there! t

1 0

Networking between KVM and containers
by sven＠svenschwermer.de 11 May '23

11 May '23

Hi, I have a host running Debian Bullseye (Podman v3.0.1). On that host, I run an OPNsense VM via KVM. The goal is to create a (virtual) network connection between that VM and one or more Podman containers. So far, I have created a dedicated bridge network for the VM via this network definition: <network connections='1'> <name>services</name> <uuid>884d7543-91b0-4752-93b7-7efc6633d733</uuid> <bridge name='virbr1' stp='on' delay='0'/> <mac address='52:54:00:78:f8:79'/> <ip address='192.168.50.1' netmask='255.255.255.0'> </ip> </network> I then created this network for Podman: [ { "cniVersion": "0.4.0", "name": "services", "plugins": [ { "ipam": { "gateway": "192.168.50.2", "routes": [ { "dst": "0.0.0.0/0" } ], "subnet": "192.168.50.0/24", "type": "host-local" }, "master": "virbr1", "type": "macvlan" } ] } ] The container is is started like so: podman run --network=services --ip=192.168.50.10 [...] This does work, however, it doesn't seem ideal. Is there a better way to achieve networking between VM and containers? Is there a way to make Podman actually configure networking by making DHCP requests (to the OPNsense VM)? That way, DNS would be configured properly as well. Any pointers are welcome 😄 Thanks, Sven

2 1

'system reset' makes things weird - ?
by lejeczek 10 May '23

10 May '23

Hi guys. I'm seeing something strange and I hoped experts/devel would comment, on: -> $ podman network ls NETWORK ID NAME DRIVER 2f259bab93aa podman bridge -> $ podman system reset --force -> $ podman network ls WARN[0000] Error validating CNI config file /etc/cni/net.d/87-podman-bridge.conflist: [failed to find plugin "bridge" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin] failed to find plugin "portmap" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin] failed to find plugin "firewall" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin] failed to find plugin "tuning" in path [/usr/local/libexec/cni /usr/libexec/cni /usr/local/lib/cni /usr/lib/cni /opt/cni/bin]] NETWORK ID NAME DRIVER 2f259bab93aa podman bridge then I ssh-log out & in, things seem okey: -> $ podman network ls NETWORK ID NAME DRIVER 2f259bab93aa podman bridge and if I 'reset' then in circles it goes. what is actually happening here? Is system setup/installation missing something? many thanks, L.

4 4

dnf update
by Dewayne Branch 09 May '23

09 May '23

Every time i do dnf update I can not download or update podman Error: Failed to download metadata for repo 'shiftkey': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Copr repo for podman4 owned by rhcontainerbot 135 B/s | 341 B 00:02 Errors during downloading metadata for repository 'copr:copr.fedorainfracloud.org:rhcontainerbot:podman4': - Status code: 404 for https://download.copr.fedorainfracloud.org/results/rhcontainerbot/podman4/f… (IP: 18.66.161.75) Error: Failed to download metadata for repo 'copr:copr.fedorainfracloud.org:rhcontainerbot:podman4': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

3 2

Networking between KVM and containers
by Sven Schwermer 04 May '23

04 May '23

Hi, I have a host running Debian Bullseye (Podman v3.0.1). On that host, I run an OPNsense VM via KVM. The goal is to create a (virtual) network connection between that VM and one or more Podman containers. So far, I have created a dedicated bridge network for the VM via this network definition: <network connections='1'> <name>services</name> <uuid>884d7543-91b0-4752-93b7-7efc6633d733</uuid> <bridge name='virbr1' stp='on' delay='0'/> <mac address='52:54:00:78:f8:79'/> <ip address='192.168.50.1' netmask='255.255.255.0'> </ip> </network> I then created this network for Podman: [ { "cniVersion": "0.4.0", "name": "services", "plugins": [ { "ipam": { "gateway": "192.168.50.2", "routes": [ { "dst": "0.0.0.0/0" } ], "subnet": "192.168.50.0/24", "type": "host-local" }, "master": "virbr1", "type": "macvlan" } ] } ] The container is is started like so: podman run --network=services --ip=192.168.50.10 [...] This does work, however, it doesn't seem ideal. Is there a better way to achieve networking between VM and containers? Is there a way to make Podman actually configure networking by making DHCP requests (to the OPNsense VM)? That way, DNS would be configured properly as well. Any pointers are welcome :) Thanks, Sven

1 0