<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Image-Cache on Solo</title><link>https://solo.hiero.org/tags/image-cache/</link><description>Recent content in Image-Cache on Solo</description><generator>Hugo</generator><language>en</language><atom:link href="https://solo.hiero.org/tags/image-cache/index.xml" rel="self" type="application/rss+xml"/><item><title>Solo Image Cache</title><link>https://solo.hiero.org/docs/advanced-solo-setup/image-cache/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/advanced-solo-setup/image-cache/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A Solo network runs roughly 29 container images (consensus node, mirror node,
JSON-RPC relay, Explorer, MinIO, and supporting services).
The &lt;strong&gt;image cache&lt;/strong&gt; pre-pulls those images and stores them as local &lt;code&gt;.tar&lt;/code&gt;
archives, so repeat deployments load them from disk instead of re-downloading
them from their registries.&lt;/p&gt;
&lt;p&gt;Solo populates and uses the cache automatically in two places:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;At install time&lt;/strong&gt; - Homebrew and npm installs pre-pull the default images.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;During &lt;code&gt;solo one-shot&lt;/code&gt; deploys&lt;/strong&gt; - Solo pulls and loads the cached images
as pipeline phases before the network is deployed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can also manage the cache directly with the &lt;code&gt;solo cache image&lt;/code&gt; commands.&lt;/p&gt;</description></item></channel></rss>