<detailsclass="tip"><summary>Pre v4.0.0 solution</summary><p>Before we added the <code>--registry-config</code> flag in k3d v4.0.0, you had to bind-mount the file to the correct location: <code>--volume "/home/YOU/my-registries.yaml:/etc/rancher/k3s/registries.yaml"</code></p>
</details>
<p>This file is a regular <ahref="https://rancher.com/docs/k3s/latest/en/installation/private-registry/">k3s registries configuration file</a>, and looks like this:</p>
<p>This file is a regular <ahref="https://rancher.com/docs/k3s/latest/en/installation/private-registry/">k3s registries configuration file</a>, and looks like this:</p>
<em>pulled</em> from the registry running at <code>http://my.company.registry:5000</code>.</p>
<em>pulled</em> from the registry running at <code>http://my.company.registry:5000</code>.</p>
<p>Note well there is an important limitation: <strong>this configuration file will only work with k3s >= v0.10.0</strong>. It will fail silently with previous versions of k3s, but you find in the <ahref="#k3s-old">section below</a> an alternative solution.</p>
<p>Note well there is an important limitation: <strong>this configuration file will only work with k3s >= v0.10.0</strong>. It will fail silently with previous versions of k3s, but you find in the <ahref="#k3s-old">section below</a> an alternative solution.</p>
<p>This file can also be used for providing additional information necessary for accessing some registries, like <ahref="#authenticated-registries">authentication</a> and <ahref="#secure-registries">certificates</a>.</p>
<p>This file can also be used for providing additional information necessary for accessing some registries, like <ahref="#authenticated-registries">authentication</a> and <ahref="#secure-registries">certificates</a>.</p>
<h3id="registries-configuration-file-embedded-in-k3ds-simpleconfig">Registries Configuration File embedded in k3d’s SimpleConfig<aclass="headerlink"href="#registries-configuration-file-embedded-in-k3ds-simpleconfig"title="Permanent link">¶</a></h3>
<p>If you’re using a <code>SimpleConfig</code> file to configure your k3d cluster, you may as well embed the registries.yaml in there directly:</p>
<p>Here, the config for the k3d-managed registry, created by the <code>create: true</code> flag will be merged with the config specified under <code>config: |</code>.</p>