On Wed, Oct 07, 2020 at 06:39:43PM -0300, Antonio Terceiro wrote: > Package: podman > Version: 2.0.6+dfsg1-1 > Severity: normal > Tags: patch > > I was testing some things that I usually run against docker with podman, > and discovered that --init does not work: > > $ docker run --init debian echo Hello world > Hello world > $ podman run --init debian echo Hello world > Error: container-init binary not found on the host: stat > /usr/libexec/podman/catatonit: no such file or directory > > I found https://github.com/containers/podman/issues/4159 upstream > > I did a quick packaging of catatonit, installed it, and with the > attached patch, I can make it work. I have just submitted an ITP for > catatonit. > > $ podman run --init debian echo Hello world > Hello world > > Should I go ahead and upload catatonit? Or would you rather point to a > different init by default? It seems we have quite some of them in the > archive already (tini, dumb-init, ...)?
Hi, ping. It would be nice to have some feedback on this, so we can make --init work out of the box. Should I upload catatonit? Should I make it provide /usr/libexec/podman/catatonit, or are you willing to apply my patch to src:libpod?
signature.asc
Description: PGP signature
