init-path and should it be statically linked?
<podman@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.2_a... $ 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?
On 2019-11-21 17:39, Muayyad AlSadi wrote:
<podman@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.2_a... $ 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?
If the primary purpose of dumb-init is to be used in containers, then it needs to be statically-linked; mounting a dynamic binary into a container is asking for trouble. I thought we were trying to get catatonit packaged for Fedora as the intended primary init binary for `podman run --init` but I'm not sure where those efforts stand. Thanks, Matt Heon
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
On 12/10/19 10:24 AM, Matt Heon wrote:
On 2019-11-21 17:39, Muayyad AlSadi wrote:
<podman@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.2_a...
$ 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?
If the primary purpose of dumb-init is to be used in containers, then it needs to be statically-linked; mounting a dynamic binary into a container is asking for trouble.
I thought we were trying to get catatonit packaged for Fedora as the intended primary init binary for `podman run --init` but I'm not sure where those efforts stand.
Thanks, Matt Heon
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
Please open a bugzilla on dumb-init. No idea on catatonit Jindich? Lokesh?
participants (3)
-
Daniel Walsh -
Matt Heon -
Muayyad AlSadi