Configure custom registry

hi what’s the correct way to add a custom registry.yaml file to RD k3s? in k3d i do something like this: --volume "$cfgDir/registries.yaml:/etc/rancher/k3s/registries.yaml" thanks in advance

[himslm01]

Copying here from Slack…

With Rancher Desktop v0.7.0, for using local insecure registries:

• When the Container Runtime is containerd you need to make /etc/rancher/k3s/registries.yaml with mirrors, as shown below. Here the mirrors act like aliases, so I can have a deployments spec.template.spec.containers[].image refer to nexus.lan/image:tag and containerd will pull the image from http://nexus.lan:8082

• When the Container Runtime is dockerd (moby) you need to make /etc/docker/daemon.json with insecure-registries and registry-mirrors as shown below. But there are two problems as far as I can see.

  • there is no possibility of having an alias - so in my example deployment the spec.template.spec.containers[].image MUST refer to nexus.lan:8082/image:tag - making the deployment yaml potentially incompatible between containerd and dockerd (moby).
  • kubernetes MUST have imagePullSecrets pointing to a secret of type kubernetes.io/dockerconfigjson defined in the deployment’s spec.imagePullSecrets or in the imagePullSecrets of the serviceaccount called default in the namespace of your deployment.

You can define both /etc/rancher/k3s/registries.yaml and /etc/docker/daemon.json in one go by creating override.yaml in the following location:

• Linux: $HOME/.local/share/rancher-desktop/lima/_config/override.yaml
• Mac: $HOME/Library/Application Support/rancher-desktop/lima/_config/override.yaml
• Windows: ???

Here’s my override.yaml

provision:
  - mode: system
    script: |
      #!/bin/sh
      set -eux
      mkdir -p /etc/rancher/k3s
      cat <<EOF >/etc/rancher/k3s/registries.yaml
      mirrors:
        docker.io:
          endpoint:
            - "http://nexus.lan:8082"
        nexus.lan:
          endpoint:
            - "http://nexus.lan:8082"
      EOF
      mkdir -p /etc/docker
      cat <<EOF >/etc/docker/daemon.json
      {
        "insecure-registries" : ["nexus.lan:8082"],
        "registry-mirrors": ["http://nexus.lan:8082"],
        "experimental": true
      }
      EOF

[jandubois]

Reference (for implementing this in the UI): private registry configuration.

A minimal implementation could just maintain a registry.yaml internally and make it editable in a text field.

Longer term a full UI (maybe driven by a schema definition) would be nice, but it should not delay exposing the functionality through the UI.