Unable to pull images from a private registry with repository prefix #8891
Closed
carloscarnero
started this conversation in
General
Replies: 1 comment 1 reply
-
It depends on your registry mirror/configuration. You might need to use a config patch instead of flags, as they have only limited support for the most simple case. If the images have a prefix in their name (vs. the registry path prefix), you can only patch all image references to use yours. If the prefix is part of the registry path (like https://www.talos.dev/v1.7/talos-guides/configuration/pull-through-cache/#using-harbor-as-a-caching-registry), you can use mirrors to redirect. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am going through the quickstart documentation, trying to bring up a local cluster with Docker, but I'm doing it under an air-gapped environment. I'm using a corporate registry where I have mirrored all the required images (as per the output of
talosctl image default
,) but they require to put those images in repositories with some prefix they gave me. For instance, instead ofexample.com:5000/siderolabs/talos:v1.7.4
I must useexample.com:5000/some/prefix/siderolabs/talos:v1.7.4
(note thesome/prefix
in the repository name.) I first tried with:which, indeed pulled the Talos image, but it wasn't able to find all the others. Which I believe is the correct outcome, since they live in a prefixed repository (and I was able to confirm by looking at the container logs.) I even tried appending the prefix to the mirrors:
but that didn't work (I expected that, since my reading of the
--registry-mirror
option is that it should be a plain URL sans path components.)So, my question is: how can I tell
talosctl
to use a prefix with all the image repositories?Beta Was this translation helpful? Give feedback.
All reactions