<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Init-Process on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/init-process/</link>
    <description>Recent content in Init-Process on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/init-process/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Container Init Processes: tini vs dumb-init vs docker-init for Signal Handling (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-22-container-init-processes-tini-dumb-init-docker-init-signal-handling-guide/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-22-container-init-processes-tini-dumb-init-docker-init-signal-handling-guide/</guid>
      <description>&lt;p&gt;Every container runs with PID 1 as its first process. This init process has a critical responsibility that most developers overlook: &lt;strong&gt;signal handling and zombie process reaping&lt;/strong&gt;. Using the wrong PID 1 process leads to containers that ignore shutdown signals, accumulate zombie processes, and refuse to stop gracefully. This guide compares three init process solutions: &lt;strong&gt;tini&lt;/strong&gt;, &lt;strong&gt;dumb-init&lt;/strong&gt;, and &lt;strong&gt;docker-init&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
