-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Open
Labels
questionFurther information is requestedFurther information is requested
Description
I encountered an issue that shows the following. Does anyone know how to resolve it?
$ sudo kubeadm init --pod-network-cidr=192.168.0.0/16 --apiserver-advertise-address=172.31.89.68 --node-name master --image-repository k8s-gcr.m.daocloud.io
I1207 03:09:13.901235 2663 version.go:256] remote version is much newer: v1.31.3; falling back to: stable-1.29
[init] Using Kubernetes version: v1.29.11
[preflight] Running pre-flight checks
[WARNING Hostname]: hostname "master" could not be reached
[WARNING Hostname]: hostname "master": lookup master on 127.0.0.53:53: server misbehaving
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
W1207 03:09:44.196963 2663 checks.go:835] detected that the sandbox image "registry.k8s.io/pause:3.8" of the container runtime is inconsistent with that used by kubeadm. It is recommended that using "k8s-gcr.m.daocloud.io/pause:3.9" as the CRI sandbox image.
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image k8s-gcr.m.daocloud.io/coredns:v1.11.1: output: E1207 03:09:44.171636 2753 remote_image.go:180] "PullImage from image service failed" err="rpc error: code = InvalidArgument desc = failed to pull and unpack image \"k8s-gcr.m.daocloud.io/coredns:v1.11.1\": Target.MediaType must be set: invalid argument" image="k8s-gcr.m.daocloud.io/coredns:v1.11.1"
time="2024-12-07T03:09:44Z" level=fatal msg="pulling image: rpc error: code = InvalidArgument desc = failed to pull and unpack image \"k8s-gcr.m.daocloud.io/coredns:v1.11.1\": Target.MediaType must be set: invalid argument"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higherReactions are currently unavailable
Metadata
Metadata
Assignees
Labels
questionFurther information is requestedFurther information is requested