- Podman - Podman List Archives

Podman API v1.0 (varlink) and libpod.conf removal notice
by Tom Sweeney 11 Dec '20

11 Dec '20

In preparation for the Podman v3.0 release, targeted for delivery on Fedora 33 in late January and other distributions soon thereafter, the varlink library that supported the Podman v1.0 API has been removed from the upstream codebase. In addition to that, the libpod.conf file that was the original file use for holding Podman configuration variables and values has also been removed from the upstream codebase. Starting with Podman v2.0, a new Podman v2.0 RESTFul API was provided to replace the v1.0 API. Around that same time, the containers.conf file was created to take the place of the libpod.conf file. Any changes to the libpod.conf file that you have made should be transferable to the containers.conf file. For more information, please see the recent post on podman.io (https://podman.io/blogs/2020/12/11/remove-varlink-libpod-conf-notice.html) Thanks to all in the community who helped Podman reach this milestone.

2 1

podman systemd demo
by Ed Haynes 09 Dec '20

09 Dec '20

I put together a small podman systemd demo for one of my customers and would be happy for comments or suggestions. It's here: https://github.com/edhaynes/podman_systemd_demo In my case the customer is pretty new to both podman and also the idea of using systemd to manage things so I wanted to keep it pretty simple and spell things out. Let me know what you think - Ed podman_systemd_demo Showing podman integration with Systemd to manage lifecycle of container For this project I created a vm based on fedora33 to act as a sandbox. Go into the fedora vm and git clone this project to run locally. Purpose is to show how podman can easily use systemd to manage lifecycle of a container. Think of a small edge device, too small to run kubernetes, but you would like to run containerized applications on it so that you can isolate application dependencies from the OS. The OS is minimal and just enough to run containers, but you would like for containers to restart if they crash and also restart automatically on reboot. For this example I'm running redis, an in-memory key value database as an example. This demo should be run as root - in fedora sudo su - There are 3 scripts. "launch_redis_container.sh" will pull the redis container, then set appropriate SELinux permissions. The containerized redis server is launched and mapped to the normal redis networking ports. Then 'podman generate systemd' creates a systemd unit file based on this container which is enabled and started. Now your containerized database is running and systemd is managing its lifecycle as a normal linux service. At this point the status of the redis-server will be shown (press "q" to get out). "test_redis_container.sh" exercises the redis database api by setting a value and then retrieving it to show the database is working. The database is then killed using pkill and you're shown how systemd creates a new container to replace it and also the recovered database is working. The systemd unit file also specifies the container to restart at startup so if you like restart the VM and verify the database is still working. cleanup.sh stops the redis-server, disables the service, and cleans up the systemd unit file and the container so you can run this demo again from the top if you like. -- Ed Haynes SOLUTIONS ARCHITECT Red Hat <https://www.redhat.com/> ehaynes(a)redhat.com *M: (978)-551-0057 * TRIED. TESTED. TRUSTED.

4 5

systemd KillMode warning
by Brian Fallik 09 Dec '20

09 Dec '20

Hi, I've been happily deploying my container services in podman using podman-generate-systemd <http://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html> unit files. Recently I noticed a scary warning in journald: XXX systemd[1]: /etc/systemd/system/container-xxx.service:21: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. This KillMode line was generated by Podman. I don't have any reason to believe that KillMode=none isn't as expected. Podman and systemd are tracking and killing my container processes correctly as far as I can tell. But the final sentence made me wonder if my unit files will suddenly stop working after a future version of systemd removes support for KillMode=none. A quick Google search and scan of Podman Github issues didn't turn up anything related so I thought I'd ask this group. Thanks, brian

2 2

problem with new alias in 2.2
by Ed Haynes 05 Dec '20

05 Dec '20

I am trying to replicate the demo given yesterday https://asciinema.org/a/376554 and not seeing the same results - this is in new fedora33 server VM, did sudo dnf install podman, enabled the updates-testing, then followed along... is there anything missing I need to install to make use of the alias? [ehaynes@localhost ~]$ sudo dnf --enablerepo=updates-testing update podman Last metadata expiration check: 0:02:22 ago on Wed 02 Dec 2020 09:25:43 AM EST. Dependencies resolved. ===================================================================================================================================================== Package Architecture Version Repository Size ===================================================================================================================================================== Upgrading: containers-common x86_64 1:1.2.0-10.fc33 updates-testing 79 k podman x86_64 2:2.2.0-2.fc33 updates-testing 11 M Transaction Summary ===================================================================================================================================================== Upgrade 2 Packages Total download size: 12 M Is this ok [y/N]: y Downloading Packages: (1/2): containers-common-1.2.0-3.fc33_1.2.0-10.fc33.x86_64.drpm 797 kB/s | 57 kB 00:00 (2/2): podman-2.2.0-2.fc33.x86_64.rpm 6.1 MB/s | 11 MB 00:01 [DRPM] containers-common-1.2.0-3.fc33_1.2.0-10.fc33.x86_64.drpm: done ----------------------------------------------------------------------------------------------------------------------------------------------------- Total 5.9 MB/s | 12 MB 00:01 Delta RPMs reduced 11.5 MB of updates to 11.5 MB (0.1% saved) Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Running scriptlet: containers-common-1:1.2.0-10.fc33.x86_64 1/1 Upgrading : containers-common-1:1.2.0-10.fc33.x86_64 1/4 Upgrading : podman-2:2.2.0-2.fc33.x86_64 2/4 Cleanup : podman-2:2.1.1-12.fc33.x86_64 3/4 Cleanup : containers-common-1:1.2.0-3.fc33.x86_64 4/4 Running scriptlet: containers-common-1:1.2.0-3.fc33.x86_64 4/4 Verifying : containers-common-1:1.2.0-10.fc33.x86_64 1/4 Verifying : containers-common-1:1.2.0-3.fc33.x86_64 2/4 Verifying : podman-2:2.2.0-2.fc33.x86_64 3/4 Verifying : podman-2:2.1.1-12.fc33.x86_64 4/4 Upgraded: containers-common-1:1.2.0-10.fc33.x86_64 podman-2:2.2.0-2.fc33.x86_64 Complete! [ehaynes@localhost ~]$ podman version Version: 2.2.0 API Version: 2.1.0 Go Version: go1.15.5 Built: Tue Dec 1 12:04:57 2020 OS/Arch: linux/amd64 [ehaynes@localhost ~]$ sudo podman network create test1 /etc/cni/net.d/test1.conflist [ehaynes@localhost ~]$ sudo podman network create test2 /etc/cni/net.d/test2.conflist [ehaynes@localhost ~]$ sudo podman run -t -d --rm --net test1 --name testctr --network-alias httpctr nginx Completed short name "nginx" with unqualified-search registries (origin: /etc/containers/registries.conf) Trying to pull registry.fedoraproject.org/nginx:latest... manifest unknown: manifest unknown Trying to pull registry.access.redhat.com/nginx:latest... unsupported: This repo requires terms acceptance and is only available on registry.redhat.io Trying to pull registry.centos.org/nginx:latest... manifest unknown: manifest unknown Trying to pull docker.io/library/nginx:latest... Getting image source signatures Copying blob 8b03f1e11359 done Copying blob d20aa7ccdb77 done Copying blob addb10abd9cb done Copying blob 852e50cd189d done Copying blob 571d7e852307 done Copying config bc9a0695f5 done Writing manifest to image destination Storing signatures 29ec6cd7cebdaa2c1e2cdd5b2b4069296050b80f8f3a7a7e504abebc1b92967c [ehaynes@localhost ~]$ sudo podman run -t -i --rm --net test1 fedora curl testctr Resolved short name "fedora" to a recorded short-name alias (origin: /etc/containers/registries.conf.d/shortnames.conf) Trying to pull registry.fedoraproject.org/fedora:latest... Getting image source signatures Copying blob 8fde7942e775 done Copying config 79fd58dc76 done Writing manifest to image destination Storing signatures <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> <style> body { width: 35em; margin: 0 auto; font-family: Tahoma, Verdana, Arial, sans-serif; } </style> </head> <body> <h1>Welcome to nginx!</h1> <p>If you see this page, the nginx web server is successfully installed and working. Further configuration is required.</p> <p>For online documentation and support please refer to <a href="http://nginx.org/">nginx.org</a>.<br/> Commercial support is available at <a href="http://nginx.com/">nginx.com</a>.</p> <p><em>Thank you for using nginx.</em></p> </body> </html> [ehaynes@localhost ~]$ sudo podman run -t -i --rm --net test1 fedora curl httpctr curl: (6) Could not resolve host: httpctr -- Ed Haynes SOLUTIONS ARCHITECT Red Hat <https://www.redhat.com/> ehaynes(a)redhat.com *M: (978)-551-0057 * TRIED. TESTED. TRUSTED.

4 6

Podman Community Meeting Notes - December 1, 2020
by Tom Sweeney 02 Dec '20

02 Dec '20

Hi All! The notes from yesterday's Podman Community Meeting are now up on podman.io (https://podman.io/community/meeting/notes/2020-12-01/) as is the video recording (https://bluejeans.com/playback/s/CaR5m0soJvtz8AOJhkvi74YnRvKbmSDDfhaeQ3f8oy…) For each topic covered during the meeting, I noted the start time of the topic in the meeting notes in case you want to skip ahead. Pablo Greco managed to add a highlight to the recording, but I was unable to post meeting. Will try to do so for future meetings to make it even easier to find to the topics there. It was great seeing and chatting with many of you yesterday. As a reminder, due to the holidays, we've decided to cancel the January meeting. So our next meeting will be February 2, 2021 at 11:00 a.m. Eastern (UTC-5). I'll send out an agenda and reminders as we close in on that. For those that celebrate, I hope you have a very happy, healthy and safe holiday season! Best Wishes, t

1 0

Podman Community Meeting - Tomorrow - Tues December 1, 2020 - 11:00 a.m. Eastern (UTC-5)
by Tom Sweeney 30 Nov '20

30 Nov '20

Hi All, Just a quick reminder that the Podman Community Meeting is tomorrow Tuesday December 1, 2020 at 11:00 a.m. Eastern (UTC-5). The agenda is online (https://podman.io/community/meeting/agenda/) and below for your reference. Video Conference on BlueJeans - https://bluejeans.com/796412039 * 11:00 -> 11:05 - Welcome! * 11:05 -> 11:15 - Matt Heon - Introducing Network Aliases * 11:15 -> 11:35 - Jhon Honce - Podman Split Brain API * 11:35 -> 11:45 - Dan Walsh - Demo containers.conf usage * 11:45 -> 11:55 - Open Forum/Questions and Answers Session * 11:55 -> 12:00 - Next Meeting, Topics for Next Meeting, and Wrap up Hope to see you there! t

1 0

concurrent podman invocations hang
by Hendrik Haddorp 30 Nov '20

30 Nov '20

Hi, I'm using podman 2.1.1 and noticed an odd behavior of podman. I created a test image that takes several minutes to stop when the container got signaled to stop. So when I call podman stop with a long timeout the call hangs a few minutes until the container stops. When I use a second terminal while the podman stop call is wating for the container to stop some podman calls hang as well. For example a podman inspect on the same container or a simple podman ps hangs. If I use ctrl-c to kill the earlier podman stop call then those hanging commands continue straight away. Are things supposed to behave that way? regards, Hendrik

4 5

Podman v2.2.0-RC1 is now available for testing
by Matt Heon 20 Nov '20

20 Nov '20

Hi All, We recently released the first release candidate for Podman v2.2.0, with a long list of new features and fixes [1]. We'd really appreciate any and all testing you'd be willing to do on this new RC. Builds are available for Fedora in Koji [2], and for most other distros they will soon be available in the Testing repos for OBS [3]. You can also build from source using the instructions at [4]. If you encounter any bugs with the new release, please file a Github issue with details. We are anticipating a final release in the new few days. The timeframe between RC and final release would normally be a little longer to allow more testing, but we want to be sure to have a release out before the upcoming holiday in the US. In the future, we'll be sure to give a longer window for feedback. Thanks, Matt Heon [1] https://github.com/containers/podman/releases/tag/v2.2.0-rc1 [2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1643508 [3] https://build.opensuse.org/package/show/devel:kubic:libcontainers:testing/p… [4] https://podman.io/getting-started/installation#building-from-scratch

2 1

Fwd: podman question
by Tom Sweeney 20 Nov '20

20 Nov '20

Daniel, Sorry about not getting back to you sooner. IDK right off the top of my head, but I've spun this off to the Podman mailing list, I'm sure folks monitoring that will have a thought or three. t -------- Forwarded Message -------- Subject: podman question Date: Wed, 18 Nov 2020 16:26:32 -0500 From: Daniel Pivonka <dpivonka(a)redhat.com> To: Tom Sweeney <tsweeney(a)redhat.com> Hi Tom, One of my coworkers pointed me to you about a podman issue I'm having. I'm hoping you can help me or point me in the right direction. I work on the ceph orchestration team and I'm facing an issue when trying to deploy containers from an authenticated registry where podman can't seem to access the registry login info. I'm trying to run containers from systemd in a way similar to this <https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atom…> The image im trying to use comes from registry.redhat.io <http://registry.redhat.io> so as a test i ran podman login first then starting my service with this unit file [Unit] Description=Redis container [Service] Restart=always ExecStart=/bin/podman run --rm --ipc=host --net=host --name ceph-a112bd2e-29d1-11eb-81b2-525400ea3cbb-node-exporter.vm-00 --user 65534 -d --conmon-pidfile /run/ceph-a112bd2e-29d1-11eb-81b2-525400ea3cbb(a)node-exporter.vm-00.service-pid --cidfile /run/ceph-a112bd2e-29d1-11eb-81b2-525400ea3cbb(a)node-exporter.vm-00.service-cid -e CONTAINER_IMAGE=registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5> -e NODE_NAME=vm-00 -v /proc:/host/proc:ro -v /sys:/host/sys:ro -v /:/rootfs:ro registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5> --no-collector.timex ExecStop=/usr/bin/podman stop -t 2 redis_server [Install] WantedBy=local.target this is similar to the unit.run file that ceph would use for its services. the service fails though and the journalctl log show that podman was not able to pull the image because of a failed authentication [root@vm-00 system]# journalctl -u test.service -- Logs begin at Wed 2020-11-18 21:04:45 UTC, end at Wed 2020-11-18 21:14:22 UTC. -- Nov 18 21:14:20 vm-00 systemd[1]: Started Redis container. Nov 18 21:14:21 vm-00 podman[9652]: 2020-11-18 21:14:21.066551744 +0000 UTC m=+0.234565900 system refresh Nov 18 21:14:21 vm-00 podman[9652]: Trying to pull registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5. <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5.>.. Nov 18 21:14:21 vm-00 podman[9652]: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions ca> Nov 18 21:14:21 vm-00 podman[9652]: Error: unable to pull registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5>: unable to pull image: Error initializing source docker://registry.redhat.io/openshift4/ <http://registry.redhat.io/openshift4/>> Nov 18 21:14:21 vm-00 systemd[1]: test.service: Main process exited, code=exited, status=125/n/a Nov 18 21:14:21 vm-00 systemd[1]: test.service: Failed with result 'exit-code'. Nov 18 21:14:21 vm-00 systemd[1]: test.service: Service RestartSec=100ms expired, scheduling restart. i did a little more debugging and it seems that systemd does not know where the auth file is Nov 18 21:19:09 vm-00 systemd[1]: Started Redis container. Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Reading configuration file \"/usr/share/containers/libpod.conf\"" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Merged system config \"/usr/share/containers/libpod.conf\": &{{false false false false false true} 0 { [] [] []} docker:// runc map[crun:[/usr/bin/crun /usr/sbin/crun /usr/local/bin/crun /usr/local/sbin/crun /sbin/crun /bin/crun /run/current-system/sw/bin/crun] kata-fc:[/usr/bin/kata-fc] kata-> Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Using conmon: \"/usr/bin/conmon\"" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Using graph driver overlay" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Using graph root /var/lib/containers/storage" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Using run root /var/run/containers/storage" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Using static dir /var/lib/containers/storage/libpod" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Using tmp dir /var/run/libpod" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Using volume path /var/lib/containers/storage/volumes" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Set libpod namespace to \"\"" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="[graphdriver] trying provided driver \"overlay\"" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="cached value indicated that overlay is supported" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="cached value indicated that metacopy is being used" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="cached value indicated that native-diff is not being used" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=warning msg="Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="backingFs=extfs, projectQuotaSupported=false, useNativeDiff=false, usingMetacopy=true" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Initializing event backend journald" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=warning msg="Error initializing configured OCI runtime kata-qemu: no valid executable found for OCI runtime kata-qemu: invalid argument" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=warning msg="Error initializing configured OCI runtime kata-fc: no valid executable found for OCI runtime kata-fc: invalid argument" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="using runtime \"/usr/bin/runc\"" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=warning msg="Error initializing configured OCI runtime crun: no valid executable found for OCI runtime crun: invalid argument" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=warning msg="Error initializing configured OCI runtime kata-runtime: no valid executable found for OCI runtime kata-runtime: invalid argument" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=info msg="Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman-bridge.conflist" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=warning msg="Default CNI network name podman is unchangeable" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="parsed reference into \"[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev,metacopy=on]registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\ <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\>"" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="reference \"[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev,metacopy=on]registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\ <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\>" does not resolve to an image ID" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="parsed reference into \"[overlay@/var/lib/containers/storage+/var/run/containers/storage:overlay.mountopt=nodev,metacopy=on]registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\ <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\>"" Nov 18 21:19:09 vm-00 podman[10481]: Trying to pull registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5. <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5.>.. Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="reference rewritten from 'registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5>' to 'registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5>'" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Trying to access \"registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\ <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\>"" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Credentials not found" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Using registries.d directory /etc/containers/registries.d for sigstore configuration" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg=" Using \"default-docker\" configuration" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg=" No signature storage configuration found for registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5>" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Looking for TLS certificates and private keys in /etc/docker/certs.d/registry.redhat.io <http://registry.redhat.io>" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="GET https://registry.redhat.io/v2/" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Ping https://registry.redhat.io/v2/ status 401" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="GET https://registry.redhat.io/auth/realms/rhcc/protocol/redhat-docker-v2/auth?…" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Server response when trying to obtain an access token: \n\"unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication\"" Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Accessing \"registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\ <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5\>" failed: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.c> Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=debug msg="Error pulling image ref //registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5>: Error initializing source docker://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5>: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registr> Nov 18 21:19:09 vm-00 podman[10481]: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication Nov 18 21:19:09 vm-00 podman[10481]: time="2020-11-18T21:19:09Z" level=error msg="unable to pull registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5>: unable to pull image: Error initializing source docker://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5 <http://registry.redhat.io/openshift4/ose-prometheus-node-exporter:v4.5>: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red > Nov 18 21:19:09 vm-00 systemd[1]: test.service: Main process exited, code=exited, status=125/n/a Nov 18 21:19:09 vm-00 systemd[1]: test.service: Failed with result 'exit-code'. Nov 18 21:19:09 vm-00 systemd[1]: test.service: Service RestartSec=100ms expired, scheduling restart. running 'podman login --get-login registry.redhat.io <http://registry.redhat.io>' always shows im logged in though. Are you aware of any reason why it seems like when running a container from systemd it cant access the auth file to pull the container first? If you need anymore info or want to see it happen live im more than happy to set up a meeting or something just let me know. Thank you! -Daniel Pivonka

3 2

Podman Community Meeting - Tues December 1, 2020 - 11:00 a.m. Eastern (UTC-5)
by Tom Sweeney 18 Nov '20

18 Nov '20

Hi All, The agenda for the next Podman Community Meeting has just been posted: https://podman.io/community/meeting/agenda/ The meeting is happening on Tuesday December 1, 2020 at 11:00 a.m. Eastern (UTC -5) and the the topics for the meeting are: * Introducing Network Aliases - Matt Heon * Podman Split Brain API - Jhon Honce * Demo of the new containers.conf usage - Dan Walsh * Open Forum and Discussion - All The meeting will be held on BlueJeans and we'll record and post the recording on podman.io. Video conference and more details on the Agenda page. Hope to see you there! t

1 0