Default Non-Interactive Dockerfile Hangs without TINI

[PVDecker1]

The default entrypoint for the non-interactive dockerfile hangs for me, at least in my environment. I was able to get around this by incorporating the changes outlined here. Once applied, I no longer experienced the hang.

[prabhakk-mw]

Hi @PVDecker1

Have you tried using the '--init' flag with your docker run command ?

docker run --init <rest of the command>

Does that also hang in your environment for the image not built with TINI directly?

[PVDecker1]

@prabhakk-mw, that seemed to do the trick. Seems to be a requirement in order to run this container. Would love to see it built into the container but at least I can make this work without injecting too much code. Thanks!

EDIT: I think the only reason I noticed this was that I did not have to pass the --init flag before, it was only the introduction of xvfb (which I am grateful for) that caused the built docker to stop working without the --init flag.

[prabhakk-mw]

Thats great to hear!
This approach is documented in the main README of this repository.

I suspect the reason it is not built into the images is because tini is not available on all the flavors of linux that we were supporting at the time, and requires different installation steps based on the flavor of linux.

Also given that TINI is now natively built into Docker 1.13+ onwards through the --init flag we chose to document this in the README instead.

We will have another look at using TINI directly with as many entrypoints as we can.

Thank you for reaching out and sharing your feedback.