You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I set the aliyun register-mirrors when ran the shell. And I can download docker.io/busybox image by "docker create docker.io/busybox". But when I executed "kubectl --kubeconfig /etc/kubernetes/admin.conf create -f test.yaml", Nothing happened. no image was downloaded.
test.yaml like below:
apiVersion: v1
kind: Pod
metadata:
name: test
spec:
containers:
- name: test-container
image: docker.io/busybox
command: [ "/bin/sh", "-c", "env" ]
The text was updated successfully, but these errors were encountered:
@danielxiaozhu Can you remove the docker.io/ part from the image name and rerun the test for me?
Actually I think there should be no problem to pull the image because you can pull the image use docker. I'm just guessing we've bypassed the --registry-mirror config if we use docker.io/busybox instead of busybox alone.
Another possible explanation is that some ips for the cdn docker registry use are not blocked. If you didn't use --registry-mirror, you can not reliably pull the image but sometimes it will work. Try delete the image the pull the image for multiple times to validate this idea.
I set the aliyun register-mirrors when ran the shell. And I can download docker.io/busybox image by "docker create docker.io/busybox". But when I executed "kubectl --kubeconfig /etc/kubernetes/admin.conf create -f test.yaml", Nothing happened. no image was downloaded.
test.yaml like below:
apiVersion: v1
kind: Pod
metadata:
name: test
spec:
containers:
- name: test-container
image: docker.io/busybox
command: [ "/bin/sh", "-c", "env" ]
The text was updated successfully, but these errors were encountered: