-
Notifications
You must be signed in to change notification settings - Fork 713
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
kubeadm tries to pull k8s.gcr.io/pause-amd64:3.1
instead of k8s.gcr.io/pause:3.1
#962
Comments
Problem solved. Suggest to add this information is the kubeadm init error log |
@luxas: GitHub didn't allow me to assign the following users: rosti. Note that only kubernetes members and repo collaborators can be assigned. 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. |
k8s.gcr.io/pause-amd64:3.1
instead of k8s.gcr.io/pause:3.1
Automatic merge from submit-queue (batch tested with PRs 65946, 65904, 65913, 65906, 65920). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. kubeadm: pause image should be arch agnostic, as it is a manifest list Signed-off-by: Davanum Srinivas <davanum@gmail.com> **What this PR does / why we need it**: `pause` image is backed by a manifest list. so we should not use the arch image when reporting using say `kubeadm config image list` **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes kubernetes/kubeadm#962 **Special notes for your reviewer**: **Release note**: ```release-note kubeadm: Fix pause image to not use architecture, as it is a manifest list ```
I originally had 'k8s.gcr.io/pause:3.1' then I tried 'k8s.gcr.io/pause-amd:3.1' - neither image had any effect on this issue. |
@bladerunner512 check your kubelet logs which tells you what need to be downloaded |
This does not appear to be an issue with local images missing. When looking at the running kubelet I noticed no args like there were in previous releases. This has changed in v1.11 from hard-coded parameters to structured config file. When I added back previous 10-kubeadm.conf from v1.10 to /etc/systemd/system/kubelet.service.d the installation proceeded correctly. Previous 10-kubeadm.conf from v1.10: config.yaml from v1.11 in /var/lib/kubelet:
kubeadm-flags.env: |
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
kubeadm version:
Environment:
uname -a
): Linux 4.4.0-62-generic --service-cidr option should set DNS server IP #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/LinuxWhat happened?
The
kubeadm init --kubernetes-version=v1.11.0 --pod-network-cidr=10.244.0.0/16
command hang onI have pre downloaded all the docker images (version matched).
and I use
docker ps -a
, these is NO any kubernetes related docker at allWhat you expected to happen?
init
to be finishedHow to reproduce it (as minimally and precisely as possible)?
I followed the instruction on the kubernetes tutorial, just kube init.
Anything else we need to know?
The text was updated successfully, but these errors were encountered: