This message was deleted.
# k3s
a
This message was deleted.
c
the
latest
tag is always pulled by default
it sounds like your private registry isn’t set up quite right?
and also maybe you don’t want to use the
latest
tag
j
Yeah it's certainly possible. What's interesting, after switching to not have the
latest
tag, I see the event about my private registry grabbing the new tag. But it still fails trying to talk to the
docker
library. What's odd about that is that it tries to pull
latest
still.
Copy code
mirrors:
  registry.test:
configs:
  "registry.test":
    tls:
      cert_file: /var/lib/rancher/k3s/certs/registry/cert.pem
      key_file: /var/lib/rancher/k3s/certs/registry/key.pem
      ca_file: /var/lib/rancher/k3s/certs/registry/ca.pem
      insecure_skip_verify: true
This is my actual config inside of
/etc/rancher/k3s/registries.yaml
. When I made this change, I did restart
k3s
.