March 2022 - Podman - Podman List Archives

Anyone seen Podman Exit Code 1 Error when pulling multiple images?
by Christopher.Miller＠gd-ms.com 17 Mar '22

17 Mar '22

Running Podman v3.4.2 and when trying to pull multiple images from an on-prem with Podman we are seeing the following error message: Podman Exit Code 1 Along with the following error output: ERRO[0000] Error refreshing volume 0d947f52c097215a516f417e1df5a1fdbf1014743a656ca2d8a8f039d226ad1c: error acquiring lock 3 for volume 0d947f52c097215a516f417e1df5a1fdbf1014743a656ca2d8a8f039d226ad1c: file exists Right now if we log out of quay via CLI and then log back in, the errors stop. A quick search finds this, not sure if I'm on the correct path or not: https://docs.podman.io/en/latest/markdown/podman-container-exists.1.html If so, these containers do exist in our on-prem registry. Thanks Chris Miller Altron INC. 703-814-7647 Christopher.miller(a)altroninc.com Christopher.Miller(a)gd-ms.com<mailto:Christopher.Miller@gd-ms.com>

3 7

DHCP lease from physical network not working for container - network is down error
by Christopher.Miller＠gd-ms.com 16 Mar '22

16 Mar '22

We're trying to pilot Prometheus services as a container in our enclave (along with the node exporter and Grafana). This is with podman 3.4.2 on RHEL 8.1. I'm using the following URL as a reference to try and setup DHCP services from the physical network for the Prometheus container. We are doing it this way so anyone on the network with a web browser can reach the UI. https://www.redhat.com/sysadmin/leasing-ips-podman I setup a .conflist file under /etc/cni/net.d created the following file: 91-prometheus.conflist (just gave it a generic name, wasn't sure if there was a naming convention) <================================== { "cniVersion": "0.4.0", "name": "prod_network", (name of prod_network) <============================== "plugins": [ { "type": "macvlan", "master": "eno1", "ipam": { "type": "dhcp" } } ] } I enable and started the following .socket file [user_a@computer_a net.d]$ sudo systemctl list-unit-files --type=socket | grep -i "podman" io.podman.dhcp.socket enabled [user_a@computer_a net.d]$ sudo systemctl status io.podman.dhcp.socket ? io.podman.dhcp.socket - DHCP Client for CNI Loaded: loaded (/usr/lib/systemd/system/io.podman.dhcp.socket; enabled; vendor preset: disabled) Active: active (running) since Fri 2022-02-25 13:41:44 EST; 1 weeks 3 days ago Listen: /run/cni/dhcp.sock (Stream) CGroup: /system.slice/io.podman.dhcp.socket Feb 25 13:41:44 computer_a systemd[1]: Listening on DHCP Client for CNI. [user_a@computer_a net.d]$ sudo systemctl is-enabled io.podman.dhcp.socket enabled [user_a@computer_a net.d]$ sudo systemctl status io.podman.dhcp.service ? io.podman.dhcp.service - DHCP Client CNI Service Loaded: loaded (/usr/lib/systemd/system/io.podman.dhcp.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2022-03-07 15:11:45 EST; 1h 35min ago Main PID: 49378 (dhcp) Tasks: 7 (limit: 45874) Memory: 9.1M CGroup: /system.slice/io.podman.dhcp.service ??49378 /usr/libexec/cni/dhcp daemon Mar 07 15:16:19 computer_a dhcp[49378]: 2022/03/07 15:16:19 network is down Mar 07 15:16:19 computer_a dhcp[49378]: 2022/03/07 15:16:19 retrying in 3.131274 seconds Mar 07 15:16:32 computer_a dhcp[49378]: 2022/03/07 15:16:32 no DHCP packet received within 10s Mar 07 15:16:32 computer_a dhcp[49378]: 2022/03/07 15:16:32 retrying in 7.313039 seconds Mar 07 15:16:49 computer_a dhcp[49378]: 2022/03/07 15:16:49 no DHCP packet received within 10s Mar 07 15:16:49 computer_a dhcp[49378]: 2022/03/07 15:16:49 retrying in 15.601824 seconds Mar 07 15:17:15 computer_a dhcp[49378]: 2022/03/07 15:17:15 no DHCP packet received within 10s Mar 07 15:17:15 computer_a dhcp[49378]: 2022/03/07 15:17:15 retrying in 32.030425 seconds Mar 07 15:17:58 computer_a dhcp[49378]: 2022/03/07 15:17:58 no DHCP packet received within 10s Mar 07 15:17:58 computer_a dhcp[49378]: 2022/03/07 15:17:58 retrying in 64.627280 seconds [user_a@computer_a net.d]$ sudo systemctl is-enabled io.podman.dhcp.service enabled [user_a@computer_a net.d]$ sudo podman run -dit --name tcs_prometheus --net=prod_network -p 9090:9090 --privileged -v /etc/prometheus/prometheus.yml:/etc/prometheus/prometheus.yml docker.io/bitnami/prometheus:latest ERRO[0164] error loading cached network config: network "prod_network" not found in CNI cache WARN[0164] falling back to loading from existing plugins on disk The container never runs, just shows started status and then outputs the ERRO and WARN. Since it doesn't run, can't look at the logs for it. Where is the best place to start to troubleshoot this? As I followed the directions from the article step-by-step. Also is there a better way to present a container to our prod network that is running local on my RHEL workstation? Thanks Chris Miller Altron INC. 703-814-7647 Christopher.miller(a)altroninc.com Christopher.Miller(a)gd-ms.com<mailto:Christopher.Miller@gd-ms.com>

5 8

Podman Community Cabal Meeting, Thur March 17, 2022 at 11:00 a.m. EDT (UTC-5)
by Tom Sweeney 15 Mar '22

15 Mar '22

The next Podman Cabal meeting is happening in 44 hours on Thurs March 17, 2022, at 11:00 am EDT (UTC-5). We'll be talking /etc/hosts in containers, macOS volumes, and room for your topics! Wearing green is optional, but strongly encouraged. The meeting is free, and the video conference link is in the agenda: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both Hope to see you there! t

1 0

docker-compose / podman.sock for mist.io Cloud Mng Platform
by Dan 11 Mar '22

11 Mar '22

Hi all, Recently I tried to run docker-compose with some example compose files and they all worked very nice. Great job! And thank you! The only thing that I cannot run is https://github.com/mistio/mist-ce After modifying image paths from "abc" to "docker.io/library/abc <http://docker.io/library/abc>" I can run docker-compose.yml with Podman 3.4.4 without errors and all containers that would normally run with Docker do run after docker-compose up -d. So it's difficult to say what went wrong... If you look at the compose: https://github.com/mistio/mist-ce/releases/download/v4.6.2/docker-compose.y… It's definitely complicated so it doesn't surprise me that something broke. Has anyone tried please? Thank you. Kind regards, Dan

2 1

insecure local repo - can it be insecure at all?
by lejeczek 09 Mar '22

09 Mar '22

Hi guys Various "howtos" on the net rarely mention SSL and I get - after such repo deployment - 'pull' complaining about HTTP, until I added certs. Question - perhaps it's not allowed by recent 'podman' versions to have insecure repo? my 'registries.conf': [registries.search] registries = ["mine.private:5000", "registry.fedoraproject.org", "registry.access.redhat.com", "registry.centos.org", "quay.io", "docker.io"] [registries.insecure] registries = ['mine.private:5000'] many thanks, L.

2 1

Running a pod on OSX leaves infra container running forever
by dav.alejandro＠gmail.com 08 Mar '22

08 Mar '22

I am running a pod via play kube. My container exits, but the companion infra container keeps running forever, meaning that the whole pod keeps running forever Is there a way to make infra container exit once pod's containers exit? I am running on OSX

2 1

make local repo HA
by lejeczek 05 Mar '22

05 Mar '22

Hi guys. Having a local repo - what would need to done to replicate it over to another host? Only mapped volume of the container '/var/lib/registry' being synced over does not seem to be enough, so I presume it would have to whole container image but, how would that work? And very next thing I'd wonder is - is separate storage path per image allowed or even possible? Or maybe there is another ready-made solution I'm unaware of? many thanks, L.

2 2

Help Needed - podman and bgp
by Filipe Carvalho 02 Mar '22

02 Mar '22

Hi team, First of all, thanks for Podman. I'm working in a service which will have a pod with 3 containers. This service (syslog relay) will be served in the network via an Anycast IP. I've BGP peering working with bird. Each pair peer and interface have a dedicated routing table. Pod is also working and configured in rootless mode, configured with network configures as slirp4netns:port_handler=slirp4netns Quick diagram to explain my problem. +--------+ +--------+ | | | | | peer 1 | | peer 2 | | | | | +--------+ +--------+ +------------------------------+ | | | int 1 int 2 int 3 | | | | dummy | | | | ip anycast | | | Host +------------------------------+ At this time, the pod is running and if I send syslog to IP in interface 3 (int 3, in routing table main), the messages arrive at container (tcp or udp). But if the messages are sent to Anycast IP (configured in interface dummy) it does not arrive at containers. I've already saw to possibilities to solve the problem: - Rudolf Vesely (DIY networking for rootless containers/pods)[1] - Using Calico CNI with podman But, before deep dive in more complex solutions, I'm requesting your help to see if I missing some more basic in my configuration. I'm trying to keep the configuration as simple as possible because in future this solutions will be supported by a team which as less knowledge in this than me. [1] https://lists.podman.io/archives/list/podman@lists.podman.io/thread/W6MCYO6… Thanks in advance. Filipe

1 0