Replies: 1 comment 1 reply
-
The error you're seeing is from what the container experiences as a DNS resolver. I have seen this "server misbehaving" error message before for DNS resolution in kubernetes. I can't recall exactly how I have solved for that, but some things to consider: • Try using the registry's cluster-local service hostname to access it. Usually something like "docker-registry.default.svc.cluster.local" (replace "default" with the namespace in which the registry is installed, if different) This should resolve regardless of service type. Make sure to use the service port (vs the pod port), if they differ. • Is that 10.x IP in the error the expected IP of your cluster's DNS resolver? It would be the IP address of the core-dns pod or service. If it doesn't match, then it's possible that something, somewhere, is overriding that resolver IP. There shouldn't be anything inherently limiting about this chart or the underlying registry image that would prevent it being used in the way you're describing. Hopefully this helps point you in the direction of a solution, and if not, perhaps others have encountered similar issues and recall a more precise remedy! |
Beta Was this translation helpful? Give feedback.
-
Hi! I have a github action runner inside the same cluster as this docker_registry. However, i'm unable to push files to it. As I am not leaving the cluster, I should not need an ingress. See the path I use below. Is there anything obviously wrong here?
Beta Was this translation helpful? Give feedback.
All reactions