<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lazy-Pulling on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/lazy-pulling/</link>
    <description>Recent content in Lazy-Pulling on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/lazy-pulling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Container Image Lazy Pulling: Stargz Snapshotter vs Nydus vs SOCI Snapshotter</title>
      <link>https://www.pistack.xyz/posts/2026-05-10-container-image-lazy-pulling-stargz-nydus-soci-guide/</link>
      <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-10-container-image-lazy-pulling-stargz-nydus-soci-guide/</guid>
      <description>&lt;p&gt;Container image pulling is one of the most time-consuming steps in container deployment workflows. When a node needs to run a pod, it must first download the entire container image from a registry — every layer, every byte — before the container can start. For large images (multi-gigabyte database or ML images), this cold-start latency can range from tens of seconds to several minutes, severely impacting deployment velocity and autoscaling responsiveness.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
