January 2022 - Podman - Podman List Archives

shouldn't the current directory be the default context for "podman build"?
by Robert P. J. Day 12 Dec '24

12 Dec '24

"man podman-build" suggests that the context argument is optional: SYNOPSIS podman build [options] [context] podman image build [options] [context] ... If no context directory is specified, then Podman will assume the current working directory as the build context, which should contain the Containerfile. but if i have a directory with nothing but a Containerfile, i get: $ podman build Error: no context directory specified, and no containerfile specified $ OTOH, specifying context of current directory: $ podman build . STEP 1: FROM alpine:latest ... etc etc ... thoughts? rday

4 5

mqueue msg_max in rootless container
by Michael Ivanov 27 Nov '23

27 Nov '23

Hallo! I'm trying to run my application in podman rootless container and I stumble on following problem: my program needs /proc/sys/fs/mqueue/msg_max to be at least 256, but in running container this value is just 10. When I try to specify this parameter while running the image (--sysctl 'fs.mqueue.msg_max=256') I get the following error: Error: open /proc/sys/fs/mqueue/msg_max: Permission denied: OCI permission denied and container is not created. My host where container is being run has this parameter set to 256. How can I expose current host setting for msg_max to my container? Best regards, -- \ / | | (OvO) | Михаил Иванов | (^^^) | | \^/ | E-mail: ivans(a)isle.spb.ru | ^ ^ | |

4 10

podman container storage backup
by Michael Ivanov 20 Oct '22

20 Oct '22

Greetings, I make periodic backups of my laptop where I use some podman containers. To perform a backup I just invoke rsync to copy my /home/xxxx/.local/share/containers directory to nfs mounted filesystem. Containers are running, but quiescent, no real activity occurs. Is this a correct way to back up or is there anything special about container directory to be taken into account? As far as I understand some hash-named subdirectories are shared between different containers and images using special kind of mounts, can this lead to duplicate copies r inconsistencies? Underlying fs is btrfs. Thanks, -- \ / | | (OvO) | Михаил Иванов | (^^^) | | \^/ | E-mail: ivans(a)isle.spb.ru | ^ ^ | |

3 2

Upgrade Recommendations from 1.4.2 to 3.3.1
by Christopher.Miller＠gd-ms.com 07 Feb '22

07 Feb '22

Hello, currently running Podman 1.4.2 on RHEL 8.1 and want to upgrade 3.3.1 so we can take advantage of the newer features (like networking). I am running containers currently in the 1.4.2 environment. Is there anything to think of or do before doing an upgrade, or a best practice? 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 5

journald log driver not working
by Ranbir 01 Feb '22

01 Feb '22

Hello Everyone, I'm testing out using journald for logging from one of my containers. I think I configured it correctly, but I don't see anything in the path I passed to it. Here's the create command I used: CreateCommand": [ "podman", "run", "-d", "--name", "postgrey", "--pod", "mailman", "--volume", "postgrey:/var/spool/postfix/postgrey:Z", "--log-driver", "journald", "--log-opt", "path=/var/log/containers/postgrey.log", "postgrey" ], /var/log/containers is empty: # ls -l /var/log/containers/ total 0 Docker's docs on retrieving the logs with journalctl don't show me anything: journalctl CONTAINER_NAME=postgrey -- Logs begin at Wed 2022-01-19 17:04:20 EST, end at Tue 2022-01-25 18:40:27 EST. -- -- No entries -- Incidentally, I used podman to crate the systemd unit files for the pod and dumped them into /etc/systemd/system. I'm starting, stopping, etc the pod using systemctl. Using journald for logging means the container's logs get written to the host's journal, right? If that's true, what am I doing wrong? -- Ranbir

3 7

Why can't I run a simple /bin/bash command from root on RHEL 8.5?
by Peter Portante 31 Jan '22

31 Jan '22

Hi Folks, We are struggling to understand why we can run rootless containers on RHEL 8.5. Why can't I do the following (as described at [1]) as a non-root user: [pportant@intlab-006 ~]$ podman run --rm --name=myubi -it registry.access.redhat.com/ubi8/ubi /bin/bash [pportant@intlab-006 ~]$ echo $? 0 Shouldn't that start an interactive shell in the container? When I run as root I see: [root@intlab-006 ~]# podman run --rm --name=myubi -it registry.access.redhat.com/ubi8/ubi /bin/bash [root@intlab-006 ~]# echo $? 127 While on another RHEL 8.5 host it works just fine: [pportant@intlabproxy-002 ~]$ podman run --rm --name=myubi -it registry.access.redhat.com/ubi8/ubi /bin/bash [root@a9ef24a2578b /]# Any help would be appreciated. Thanks, -Peter [1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht…

4 10

Podman Community Meeting - Tuesday February 1, 2022 - 11:00 a.m. EST (UTC-5)
by Tom Sweeney 31 Jan '22

31 Jan '22

The Podman Community Cabal meeting is happening 20 hours from now at 11:00 am EST (UTC-5) Tues Feb 1, 2022. Agenda with conference link here: https://podman.io/community/meeting/agenda/. Video Conference: https://bluejeans.com/880216278/2568 We'll be seeing demos on the Windows Client, Podman's Desktop, Sparsefile handling, and the new Network stack that's coming in Podman v4.0 Hope to see you there! t

1 0

Problem adding a routing rule for containers before they start
by Daniel Gray 27 Jan '22

27 Jan '22

Hi, My server has multiple network interfaces. - bond0.3 <- default route via 192.168.3.1 - bond0.7 <- lower priority interface via 192.168.7.1 In this case I want my containers to be using bond0.7. I add a separate routing table and prepare default route: echo "7 CONTAINERS" >> /etc/iproute2/rt_tables sudo ip route add default via 192.168.7.1 table CONTAINERS sudo ip route add 192.168.7.1 dev bond0.7 table CONTAINERS sudo ip rule add from 10.89.0.0/24 lookup CONTAINERS For this I am using rootful containers, though I plan to adapt these to be rootless when I get them working. sudo podman network create -d bridge net1 sudo podman run -dt --name test --network net1 --cap-add NET_RAW --rm busybox sudo podman exec -it test ash / # wget -q -O - ifconfig.me Nothing......... / # ip route get 1.1.1.1 1.1.1.1 via 10.89.0.1 dev eth0 src 10.89.0.2 / # ip route default via 10.89.0.1 dev eth0 10.89.0.0/24 dev eth0 scope link src 10.89.0.2 / # traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 46 byte packets 1 128bedbab28b (10.89.0.2) 3034.227 ms !H 3039.811 ms !H 3039.875 ms !H Now if I delete the rule: sudo ip rule del from 10.89.0.0/24 lookup CONTAINERS and do something like a traceroute (which takes the default route out): traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 46 byte packets 1 host.containers.internal (10.89.0.1) 0.006 ms 0.005 ms 0.004 ms 2 192.168.3.1 (192.168.3.1) 0.562 ms 0.815 ms 0.766 ms ... then add the rule: sudo ip rule add from 10.89.0.0/24 lookup CONTAINERS / # traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 46 byte packets 1 host.containers.internal (10.89.0.1) 0.008 ms 0.005 ms 0.004 ms 2 192.168.7.1 (192.168.7.1) 0.533 ms 0.558 ms 0.440 ms it works. The issue is I want to add the routing rules when my machine boots up. I was able to reproduce the same problem with Docker. -- Daniel Gray 0x41911F722B0F9AE3 https://mastodon.social/@dngray

1 2

Thanks for blog post: How to use Podman inside of Kubernetes
by Craig Rodrigues 21 Jan '22

21 Jan '22

Hi, Many thanks to Urvashi Mohnani and Dan Walsh for this blog post: https://www.redhat.com/sysadmin/podman-inside-kubernetes I worked at a recent gig, where I replaced a very fragile "Docker-in-Docker" + /var/run/docker.setup setup with podman. This setup was used to build about 50 different containers, inside containers running in a Kubernetes cluster. The July blog post was very straightforward and easy to follow. The resulting setup with podman was solid, and didn't have the fragility of requiring mounting /var/run/docker.sock inside containers. Thanks! -- Craig

2 1

podman build --secret does not behave the same as docker
by Craig Rodrigues 21 Jan '22

21 Jan '22

Hi, I tried to use the *--secret* flag in docker as documented here: https://docs.docker.com/develop/develop-images/build_enhancements/ https://docs.docker.com/engine/reference/commandline/build/#options When I tried it in podman, it didn't work. I wrote up a bug report here: https://github.com/containers/buildah/issues/3734 Thanks. -- Craig

1 0