December 2019 - Podman - Podman List Archives

by Paulo Matos

Hi all, In docker, there is currently through buildx the possibility of building and running a container in several architectures other than the host one through the use of binfmt and qemu. Is there currently any support in podman to do this? Kind regards, -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

4 years, 10 months

2
2
0 / 0

Podman fix for kubernetes issues 76676, vulnerability publicly reported in CVE-2019-11244

by Grimmett, Tim＠FTB

When will Podman project be providing a fix for CVE-2019-11244<https://nvd.nist.gov/vuln/detail/CVE-2019-11244> related to Kubernetes v1.8.x-v1.14.x vulnerability? See - https://github.com/kubernetes/kubernetes/issues/76676 Thank you in advance for your quick reply. ______________________________________________________________________ CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email.

4 years, 10 months

2
1
0 / 0

shouldn't the current directory be the default context for "podman build"?

by Robert P. J. Day

"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 years, 11 months

2
2
0 / 0

init-path and should it be statically linked?

by Muayyad AlSadi

<podman(a)lists.podman.io>Hi, on fedora 30 as root # dnf install dumb-init let's try podman as normal user the following command does not work (busybox image) $ podman run --rm -ti --init --init-path=/bin/dumb-init busybox /bin/sh standard_init_linux.go:211: exec user process caused "no such file or directory" but when using fedora image it works $ podman run --rm -ti --init --init-path=/bin/dumb-init registry.fedoraproject.org/fedora-minimal:30 /bin/sh but when using statically and as normal user $ curl -sSL -o ~/.local/bin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.2.2/dumb-init_1.2.... $ chmod +x ~/.local/bin/dumb-init $ ldd ~/.local/bin/dumb-init not a dynamic executable $ podman run --rm -ti --init --init-path=~/.local/bin/dumb-init busybox /bin/sh it works fine so should fedora ship statically linked dumb-init?

4 years, 11 months

3
2
0 / 0

non-root usage: ping not working

by Michael Traxler

Hi, I try to run a container with podman as a normal user. It runs, but ping doesn't work: $ podman run --net=host -it docker.io/library/debian ping 192.168.0.1 ping: socket: Operation not permitted When I ommit the --net=host options, the is no error message, but still not working: $ podman run -it docker.io/library/debian ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. hangs. What should I do to get this working? I need network access to this containter from outside and for sure ping should work from the inside. Anything I missed? Thanks a lot for your help! Michael

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

Podman December 2019