Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

I cant initialize the Kubeadm #22

Open
ghulevishal opened this issue Dec 29, 2017 · 1 comment
Open

I cant initialize the Kubeadm #22

ghulevishal opened this issue Dec 29, 2017 · 1 comment

Comments

@ghulevishal
Copy link

I have Problem while creating the Kubernetes cluster using kubeadm init --pod-network-cidr=10.244.0.0/16 --ignore-preflight-errors=all --cri-socket=/var/run/crio/crio.sock. The process stuck at the

[init] This might take a minute or longer if the control plane images have to be pulled.

it gives error like

[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp 127.0.0.1:10255: getsockopt: connection refused.

Is there any documentation i can follow to configure kubeadm with CRI-O runtime

@BenHall
Copy link

BenHall commented Mar 11, 2018

Check that /var/run/crio/crio.sock exists. If it doesn't, run systemctl restart crio.service

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants