# Kernel panic starting init in a nix-built container with tini as init

**URL:** <https://community.fly.io/t/kernel-panic-starting-init-in-a-nix-built-container-with-tini-as-init/6328>\
**Category:** Questions / Help\
**Created:** [August 10, 2022, 3:58am UTC](https://community.fly.io/t/kernel-panic-starting-init-in-a-nix-built-container-with-tini-as-init/6328 "2022-08-10T03:58:59Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![eli](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/eli/32/49867_2.png) [@eli](https://community.fly.io/u/eli)\
**Post date:** [August 10, 2022, 5:49am UTC](https://community.fly.io/t/kernel-panic-starting-init-in-a-nix-built-container-with-tini-as-init/6328/7 "2022-08-10T05:49:45Z")

</div>

A bit of a long shot, but I wonder if the issue could be tini needing PID 1?  
This is just an initial guess based off the error message in your call stack, a cross-reference with our [init-snapshot repo](https://github.com/superfly/init-snapshot/blob/48cf36ff7ac6229df66bf1de2b1e2b1c233b2e51/src/bin/init/main.rs), from reading about [tini behavior on the actual-server project](https://github.com/krallin/tini/issues/130), and [on our platform more generally](https://community.fly.io/t/tini-zombie-process-with-deno-dockerfile/5495/2).

I hope this isn’t a complete misapprehension of what’s going on-- thank you so much for your awesome report 🙂

---

_[View the full topic](https://community.fly.io/t/kernel-panic-starting-init-in-a-nix-built-container-with-tini-as-init/6328)._