Tini warning when building 1.28.1 image about deno_docker

[EdJoPaTo]

--init already creates an init handler so tini is useless (which is why tini writes this warning).

Most processes (like Deno) are written to have a working init handler. Containers are meant to be pretty minimal so they only ship with the relevant processes. Container environments can add a pretty minimal init handler on run with --init which is the normal way of working with containers.

#165 added an init handler to the deno container image. So running with --init results in having two init handlers running which is what tini complains about.
While I personally would prefer to use the container environment --init handler the simplest solution with deno containers is to omit the --init on run.

The old version you mentioned (1.10.3) was probably before tini was added to this image so there wasnt a conflict of two init handlers then.

[GJZwiers]

Thanks for looking into it! Running the image without --init works for me. The page on Docker Hub for the Deno image is where I got the command from but it may be outdated, i.e. the readme on https://github.com/denoland/deno_docker doesn't use --init in docker run anymore.

[enjikaka]

Also got this issue when upgrading from 1.25 to 1.30. I run Deno in Docker via Dokku and don't handle the containers myself; so quite weird to get the Tini message in my face like this. Added ENV TINI_SUBREAPER=true to my Dockerfile to remove the error.