Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use registry mirror #749

Open
AliRezaBeitari opened this issue Dec 9, 2023 · 0 comments
Open

Cannot use registry mirror #749

AliRezaBeitari opened this issue Dec 9, 2023 · 0 comments

Comments

@AliRezaBeitari
Copy link

I'm using k3s and I have a Private Registry Configuration in which I've added a mirror:

/etc/rancher/k3s/registries.yaml:

mirrors:
  helloworld.k8s:
    endpoint:
      - "https://***************"
configs:
  "***************":
    auth:
      username: ****
      password: ****

Then, I deployed Keel using Helm, but I can see these errors in the logs:

time="2023-12-09T16:57:47Z" level=error msg="trigger.poll.manager: got error(-s) while watching images" error="encountered errors while adding images: Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/his-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host"

It seems Keel does not know helloworld.k8s is just a mirror to the actual registry endpoint.

Is there any way to tell Keel to read the /etc/rancher/k3s/registries.yaml file and act accordingly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant