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
Registry addon incompatible with multiple nodes, image pulls fail on second node #11505
Comments
This is a known problem. Help wanted! |
Hmm, the proxy is supposed to be a DaemonSet so it should be running on every node ? description here: cluster/addons/registry#expose-the-registry-on-each-node But it is also very ancient (2016), so there could be something else wrong with it (nginx). EDIT: Worked for me, though.
$ minikube kubectl -- get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-558bd4d5db-2wtm4 1/1 Running 0 103s
kube-system etcd-minikube 1/1 Running 0 104s
kube-system kindnet-95m5x 1/1 Running 0 103s
kube-system kindnet-md6b9 1/1 Running 0 52s
kube-system kube-apiserver-minikube 1/1 Running 0 119s
kube-system kube-controller-manager-minikube 1/1 Running 0 104s
kube-system kube-proxy-bk7kf 1/1 Running 0 103s
kube-system kube-proxy-xp6q7 1/1 Running 0 52s
kube-system kube-scheduler-minikube 1/1 Running 0 104s
kube-system registry-6fv4q 1/1 Running 0 103s
kube-system registry-proxy-rvlq7 1/1 Running 0 94s
kube-system registry-proxy-sh9lc 1/1 Running 0 42s
kube-system storage-provisioner 1/1 Running 0 112s
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
When starting a minikube cluster with multiple nodes, image pulls fail on the second node.
Steps to reproduce the issue:
minikube start --driver=docker --nodes=2 --cni=auto --addons=default-storageclass,registry,storage-provisioner --container-runtime=containerd
minikube-m02
node will fail withFull output of
minikube logs
command:minikube.log
Full output of failed command:
The text was updated successfully, but these errors were encountered: