January 2022 - Podman - Podman List Archives

Podman Community Cabal Meeting - Thur Jan 20, 2022 11:00 a.m. EST (UTC-5)

by Tom Sweeney

Hi All! The Podman Community Cabal Meeting happening 24 hours from now! Conference link on the agenda: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both Free to attend and hope to see you there! t

2 years, 10 months

1
0
0 / 0

Podman Community Cabal Meeting - Thurs Jan 20, 2022, 11:00 a.m. EST (UTC-5)

by Tom Sweeney

Hi All, The next Podman Community Cabal meeting is coming up next Thursday January 22, 2022 at 11:00 a.m. EST (UTC-5). On the agenda are topics concerning networks, storage on Macs, and 4.0 rollout. We also have time for any topics from the attendees. The agenda with the link to the video conference is here: https://hackmd.io/gQCfskDuRLm7iOsWgH2yrg?both and it's free to attend. Hope to see you there! t

2 years, 10 months

1
0
0 / 0

Looking for volunteers on MAC to play with podman-desktop from upstream

by Daniel Walsh

This is very early and it might totally break, but we have opened a REPO https://github.com/containers/podman-desktop This is just a tray application used for launching podman machines. Comments, issues and especially PRs are welcome.

2 years, 10 months

3
3
0 / 0

TLS Handshake Error and Exit 125 error when pulling multiple images with Podman

by Christopher.Miller＠gd-ms.com

Not sure if anyone else has seen this. We use Podman to pull multiple images from a Quay registry for building software. During this process, an image won't get pulled. We then see a TLS Handshake errors along with an exit-125 errors too. Wondering if anyone has experienced this. Thanks

2 years, 10 months

1
0
0 / 0

what replaces the -- link

by Michael Biarnes Kiefer

Hi, I am new to podman. I have this problem: The Docker option *--link* is legacy and doesn't work any-more. Using podman right now I saw that this option should be replaced somehow by *--network *or *--pod*. The thing is I tried several things with --network or --pod but somehow two different containers running (from two different images) can't communicate to each other: Before (when Docker --link still was available): $ podman images REPOSITORY TAG IMAGE ID CREATED SIZE localhost/kiegroup/kie-server-showcase 7.63.0.Final 7de306f0d498 20 minutes ago 1.03 GB localhost/kiegroup/business-central-workbench-showcase 7.63.0.Final 446a00d242c2 10 days ago 1.11 GB podman run -p 8083:8080 -p 8003:8001 -i -t --name business-central-wb kiegroup/business-central-workbench-showcase:7.63.0.Final (runs the 446a00d242c2 container) podman run -p 8088:8080 -i -t --name kieserver-wb --link business-central-wb:kie-wb kiegroup/kie-server-showcase:7.63.0.Final (run 7de306f0d498 container linked to 446a00d242c2) Both Containers could communicate and share different vars. I tried to create a network and run both containers with --network <createdNetwork> or I created a pod and run both containers with --pod <created pod> option, but somehow the running container doesn't share the needed values. I do podman inspect and look to container values - and they are there as expected. What do I wrong? podman version 3.4.4 OS: Fedora 34 ThanX Michael -- Michael Biarnés Kiefer Release engineer EMEA ENG Product-Middleware Red Hat SL Barcelona Spain <https://www.redhat.com> <https://www.redhat.com>

2 years, 10 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

Podman January 2022