-
Notifications
You must be signed in to change notification settings - Fork 706
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 init
does not use the images downloaded by kubeadm config images pull
#2751
Comments
check your containerd configurition for pause image and change it. |
yes, you need to separately set the pause image for the CR /support |
Hello, @tankilo 🤖 👋 You seem to have troubles using Kubernetes and kubeadm. Please see: |
This seems to be a very common problem for users with kubeadm + contained. Should we add some tips for users init cluster with The docs seems to be enough. |
we also mention it in the kubeadm init page |
Pretty Thanks for the answer above, i didn' go through the document. I follow a blog written by others. |
official docs are the only up-to-date source and have all the details |
According to the doc: It does work. But it was set in the config and the pause image version depends on Kubernetes version, so it cannot be That means every time I need to manually change the config in CR, it's not elegant. So do we have a better way to solve it? |
I am afraid there is no simple way. For containerd in a future release(1.7+ maybe or 2.0?), containerd starts to use sandbox API instead of a pause container. See more at containerd/containerd#4131 (comment). (BTW, For the pause image gc, there is a pinned image feature in https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2040-kubelet-cri#pinned-images. It can help for image not gc.) |
Thanks a lot! You saved me! |
What keywords did you search in kubeadm issues before filing this one?
If you have found any duplicates, you should instead reply there and close this page.
If you have not found any duplicates, delete this section and continue on.
Is this a BUG REPORT or FEATURE REQUEST?
Choose one: BUG REPORT or FEATURE REQUEST
Versions
kubeadm version (use
kubeadm version
):kubeadm version: &version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.0", GitCommit:"a866cbe2e5bbaa01cfd5e969aa3e033f3282a8a2", GitTreeState:"clean", BuildDate:"2022-08-23T17:43:25Z", GoVersion:"go1.19", Compiler:"gc", Platform:"linux/amd64"}
Environment:
kubectl version
): Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.0", GitCommit:"a866cbe2e5bbaa01cfd5e969aa3e033f3282a8a2", GitTreeState:"clean", BuildDate:"2022-08-23T17:44:59Z", GoVersion:"go1.19", Compiler:"gc", Platform:"linux/amd64"}uname -a
): Linux kmaster 3.10.0-1127.el7.x86_64 kubeadm join on slave node fails preflight checks #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64 x86_64 GNU/LinuxWhat happened?
I am in China, so i need to set
--image-repository
attribute.First, i execute
kubeadm config images pull
to download images.You can see,
registry.aliyuncs.com/google_containers/pause:3.8
is downloaded.Then i run
sudo kubeadm init --apiserver-advertise-address=172.16.16.100 --kubernetes-version v1.25.0 --image-repository registry.aliyuncs.com/google_containers --service-cidr=10.1.0.0/16 --pod-network-cidr=10.244.0.0/16
sudo journalctl -xeu kubelet
kubeadm init
didn't use the image downloaded by commandkubeadm config images pull
!What you expected to happen?
kubeadm init
use the image downloaded by commandkubeadm config images pull
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
The text was updated successfully, but these errors were encountered: