<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hooks on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/hooks/</link>
    <description>Recent content in Hooks on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/hooks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted OCI Runtime Hooks: umoci vs oci-seccomp-bpf-hook vs oci-add-hooks</title>
      <link>https://www.pistack.xyz/posts/2026-05-16-self-hosted-oci-runtime-hooks-umoci-seccomp-bpf-add-hooks-guide/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-16-self-hosted-oci-runtime-hooks-umoci-seccomp-bpf-add-hooks-guide/</guid>
      <description>&lt;p&gt;OCI (Open Container Initiative) runtime hooks allow you to execute custom logic at specific points during a container lifecycle — before it starts, after it stops, or during creation. These hooks enable powerful customization: injecting environment variables, setting up network namespaces, applying seccomp profiles dynamically, or mounting filesystems on-the-fly. In this guide, we compare three open-source OCI hook implementations and show you how to deploy each with Docker Compose.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
