-
Notifications
You must be signed in to change notification settings - Fork 539
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
coredns stuck at ContainerCreating #87
Comments
I was missing the |
Could you elaborate? I am having a similar issue, where I was trying to use the flannel plugin (which is Running) but there are 2 coredns which seem to be stuck in ContainerCreating |
@doctorCC Any errors/warnings in kubelet logs? |
Can you do `kubectl describe po coredns-78fcdf6894-sdvhr`?
…On Tue, Sep 11, 2018 at 10:56 AM chrisohaver ***@***.***> wrote:
@doctorCC <https://github.com/doctorCC> Any errors/warnings in kubelet
logs?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#87 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJB4s2gSb55lRv3dg1Ec2Rp50d91baocks5uZ_ligaJpZM4V7hUW>
.
|
I tore down the sysem and rebuilt it, allowing the emptyCluster to sit there overnight. Again there were two coredns which were never built. I tried to deploy a simple nginx, which also went into a ContainerCreating state. The logs from that were available and are below. I am running: kubectl get pods --all-namespaces Normal Scheduled 12m default-scheduler Successfully assigned default/my-nginx-7b6fc8965-24skw to ubuntu |
@doctorCC, Perhaps it's this ipv6 disabled in kernel issue... |
I'm running into the same issue, and I have IPv6 enabled. I'm using a fresh setup using
When I run
Which isn't very useful. Any luck @doctorCC? Also, @drpaneas, what do you mean by loopback for CNI? |
This is *probably* an issue with your container networking. For your
"describe", you need `-n kube-system`.
…On Fri, Oct 5, 2018 at 2:49 PM Scott Morris ***@***.***> wrote:
I'm running into the same issue, and I have IPv6 enabled. I'm using a
fresh setup using kubeadm on Ubuntu Server 18.04.
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-576cbf47c7-k2xxd 0/1 ContainerCreating 0 91m
kube-system coredns-576cbf47c7-pqk9k 0/1 ContainerCreating 0 91m
When I run describe I get the following error message,
$ kubectl describe pod coredns-576cbf47c7-pqk9k
Error from server (NotFound): pods "coredns-576cbf47c7-pqk9k" not found
Which isn't very useful.
Any luck @doctorCC <https://github.com/doctorCC>? Also, @drpaneas
<https://github.com/drpaneas>, what do you mean by loopback for CNI?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#87 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJB4s6NBlCj_JlbhztOkZp47npM3mR1Vks5uh9P7gaJpZM4V7hUW>
.
|
how exactly did u set the 'loopback'? |
Thanks @johnbelamaric for your help. I found my issue, it was a bug in Flannel (flannel-io/flannel#1044) when running on K8s 1.12. What fixed it for me was the suggestion from this comment (kubernetes/kubernetes#48798). |
|
Thank you @spitfire88! This works for me. Although I have now idea why I need to download and compile something when I'm trying to use kubeadm |
This is does not fix my issue |
executing spifire's recommended steps did not work. running this work: kubectl -n kube-system apply -f https://raw.githubusercontent.com/coreos/flannel/bc79dd1505b0c8681ece4de4c0d86c5cd2643275/Documentation/kube-flannel.yml (kubernetes/kubernetes#48798) |
docker 18.09.0,kube1.13.1
|
you should add --namespace=kube-system when you run describe pod command. |
worked for me |
Hi! I applied the deployment and the go get steps, now I get:
Please help Host: ClearLinux
Bridges:
Docker version:
|
@msq6323013 on master node or worker? |
Master node |
run this command to active flannel mode kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/2140ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel.yml |
I am also getting the same error - container creation > bash-4.2$ kubectl get pods -n kube-system Name: coredns-66bff467f8-hvhts Events: Normal Scheduled 29m default-scheduler Successfully assigned kube-system/coredns-66bff467f8-hvhts to k8s-lab-master |
spitfire88 I install go in a Nvidia AI machine with ARM64. Please see the go installation guide in the following go weblink. Afterwards, I build, test hello.go and go runs well. While I run the commands as you mentioned,
I get to know that build.sh is replaced by build_linux.sh. So I have the following configuration.
Even though it has the above message, the plugins marked with the directory have existed.
It seems the completion of the CNI plugins. However, one of the nodes is still marked with NotReady (in the ContainerCreating status). |
Following the late-shared go installation, I have solved the issue with the following setup of Flannel cluster network. 1. Configure the Flannel For ARM64 Architecture
Or For AMD64 Architecture
2. Apply Flannel and Check the Configuration 1). Apply Flannel
2). Check the Configuration Check kube-flannel-cfg
Check the Device For ARM64 Architecture
or
3. Apply RBAC
I can get all the nodes with the Status of Ready now after executing the commands on the Master node.
Notes: Before setting up the Flannel, you must complete the master node initiation of Kubernetes and worker nodes joining. Cheers. Reference
|
Such issue (stuck at ContainerCreating) happened to me because flannel was not properly installed after I created k8s cluster. I used CentOS 7.8 Pls try this how to install flannel (https://phoenixnap.com/kb/how-to-install-kubernetes-on-centos)[root@master-node ~]# kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml [Result] subnet.env is created[root@master-node flannel]# cat subnet.env coredns and dashboard became normal (running state)[root@master-node flannel]k get pods --all-namespaces -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES you can see flannel interface toocni0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 flannel.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 vethcbb22c7b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 vethff9c51c2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 |
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "0540b7e66e4e5c5aa34abefd27bf303cf901ad2bad771f2408c1d9f41952311a" network for pod "coredns-74ff55c5b-6pn9f": networkPlugin cni failed to set up pod "coredns-74ff55c5b-6pn9f_kube-system" network: stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ For me its looking for calico durectory . i am confused why it looks for calico when i am installing flannel . Any idea how to proceed further |
it worked for my issues with Calico network plugin kubectl create -f https://docs.projectcalico.org/manifests/tigera-operator.yaml kubectl create -f https://docs.projectcalico.org/manifests/custom-resources.yaml |
creating the /run/flannel/subnet.env fixes the coredns issue not starting but it's only temporary.
|
Actually, I only had to do a:
|
So here is my solution: Run the following 2 command to Down Interface and Remove it from your Master/Control-Plane Machines
|
Do you know how to change the CIDR Network IP address as private IP in any flannel config file |
I am running the latest kubeadm 1.11 where CoreDNS is the default. I've also installed weave-net plugin. However, I still cannot get coredns pod running ....
Any debug tips?
The text was updated successfully, but these errors were encountered: