# Tini zombie process with deno dockerfile

**URL:** <https://community.fly.io/t/tini-zombie-process-with-deno-dockerfile/5495>\
**Category:** General\
**Created:** [June 4, 2022, 7:13am UTC](https://community.fly.io/t/tini-zombie-process-with-deno-dockerfile/5495 "2022-06-04T07:13:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ignoramous](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@ignoramous](https://community.fly.io/u/ignoramous)\
**Post date:** [June 4, 2022, 9:43am UTC](https://community.fly.io/t/tini-zombie-process-with-deno-dockerfile/5495/2 "2022-06-04T09:43:35Z")

</div>

[Tini](https://github.com/krallin/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](https://fly.io/docs/app-guides/multiple-processes/)).

One can setup health-checks ([local](https://community.fly.io/t/non-service-health-checks/5490/3), [remote](https://fly.io/docs/reference/configuration/#services-tcp_checks), [custom](https://community.fly.io/t/healthchecks-and-private-networks/485/2)) to ensure a process is serving tcp/udp as expected.

---

_[View the full topic](https://community.fly.io/t/tini-zombie-process-with-deno-dockerfile/5495)._