Tini zombie process with deno dockerfile

1

Hello,
I am trying to get a deno application running with a dockerfile. I am able to get it working on my local machine; however, I am having trouble deploying it. I have these logs appearing whenever I try to deploy.

Zombie processes will not be re-parented to Tini, so zombie reaping won't work.

2022-06-04T07:05:16.959 app[f8952097] sjc [info] To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.

I’m not sure where I am going wrong. Do I need to do something in the dockerfile to get Tini running as PID 1? Thank you for any help.

1 Like
2

Tini cannot assume pid 1 on Fly. Run Deno as-is. On process kills, Fly init should recreate VM and start a new process therein, automatically (ref).

One can setup health-checks (local, remote, custom) to ensure a process is serving tcp/udp as expected.

3

That is correct.

Our init handles all the same things tini handles (reaping zombies) and much more.

The recommended way to run your app on Fly is to run your program directly.

2 Likes
4

Sorry to bump this, but I have a Deno app that runs a Hono server. My Dockerfile ends with

CMD ["deno, "run", "-A", "main.ts"]

When a Machine starts, I see the warning, but the app seems to work fine.

2024-10-31T18:11:25.252 app[d8dd606b316e48] mad [info] [WARN tini (322)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2024-10-31T18:11:25.252 app[d8dd606b316e48] mad [info] Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2024-10-31T18:11:25.252 app[d8dd606b316e48] mad [info] To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.

I have no idea what tini or reaping zombies is…
Can I just safely ignore this warning? Is there a way to make it go away (setting the TINI_SUBREAPER env. var to something?)

EDIT
I also see logs like this during runtime

WARN Reaped child process with pid: XXX and signal: SIGKILL, core dumped? false