Kubernetes (Kubespray) Issue.
-
Hello,
I am trying to set up Kubernetes cluster using Kubespray but on the halfway installation the playbook exit out with this error. I appreciate If I get any valuable inputs. Thanksfatal: [minion01]: FAILED! => { "attempts": 2, "changed": false, "cmd": [ "sh", "-c", "/usr/bin/docker rm -f etcdctl-binarycopy; /usr/bin/docker create --name etcdctl-binarycopy quay.io/coreos/etcd:v3.2.24 && /usr/bin/docker cp etcdctl-binarycopy:/usr/local/bin/etcdctl /usr/local/bin/etcdctl && /usr/bin/docker rm -f etcdctl-binarycopy" ], "delta": "0:00:15.312319", "end": "2018-11-12 17:36:21.077510", "invocation": { "module_args": { "_raw_params": "sh -c \"/usr/bin/docker rm -f etcdctl-binarycopy; /usr/bin/docker create --name etcdctl-binarycopy quay.io/coreos/etcd:v3.2.24 && /usr/bin/docker cp etcdctl-binarycopy:/usr/local/bin/etcdctl /usr/local/bin/etcdctl && /usr/bin/docker rm -f etcdctl-binarycopy\"", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "warn": true } }, "msg": "non-zero return code", "rc": 1, "start": "2018-11-12 17:36:05.765191", ****"stderr": "Error: No such container: etcdctl-binarycopy\nUnable to find image 'quay.io/coreos/etcd:v3.2.24' locally\nError response from daemon: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)",**** "stderr_lines": [ "Error: No such container: etcdctl-binarycopy", "Unable to find image 'quay.io/coreos/etcd:v3.2.24' locally", "Error response from daemon: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" ], "stdout": "", "stdout_lines": []
-
Added tags and stuff.
-
Looks like maybe Docker is not properly working?
-
@scottalanmiller said in Kubernetes (Kubespray) Issue.:
Looks like maybe Docker is not properly working?
Look at how surprised I am at Docker not working properly. /sarcasim
-
@devops1 are you able to manually create the directory using
/usr/bin/docker create --name etcdctl-binarycopy quay.io/coreos/etcd:v3.2.24
Is that path correct
/usr/bin/docker
? -
Sounds like you can't retrieve the docker image from the quay.io docker registry
Does it fail when you try to pull it in Docker directly?
Docker image pull quay.io/coreos/etcd:v3.2.24Are you behind a proxy? I think that's the common issue for people who experience this error.
-
@flaxking
I am behind a proxy. I did not try to pull directly from docker but I will do it and update it. Thanks for the response. -
@flaxking So, If I am behind the proxy how to solve this error? Pulling the docker image directly will knock out this error?
-
@devops1 said in Kubernetes (Kubespray) Issue.:
@flaxking So, If I am behind the proxy how to solve this error? Pulling the docker image directly will knock out this error?
No, I think you might have to tell Docker the address of your proxy server. Probably either as an environment variable on your system or in the docker config file
-
I've never done it, I just remember something about that when I was looking up the same message when I was having issues when hosting my own docker registry.
-
@flaxking We are downloading all the images and putting up everything in the J frog artifactory and creating the repos in /etc/yum.repos which is pointing to the J frog artifactory where all our yum repos and etc will be located.
So, manually download the image and set it up to the J frog ?
-
@DustinB3403
Yes, I checked the path and /usr/bin/docker and it is there. /usr/bin/docker - where docker is not a directory but seems like a Binary file.I did not understood this part in your comment - (are you able to manually create the directory using /usr/bin/docker create --name etcdctl-binarycopy quay.io/coreos/etcd:v3.2.24) .
What do you want me to create exactly?
-
@devops1 said in Kubernetes (Kubespray) Issue.:
@flaxking So, If I am behind the proxy how to solve this error? Pulling the docker image directly will knock out this error?
You need to add the systemd unit proxy settings under
/etc/systemd/system/docker.service.d/http-proxy.conf
[Service] Environment="HTTP_PROXY=http://theproxy.com" Environment="HTTPS_PROXY=http://theproxy.com" Environment="http_proxy=http://theproxy.com" Environment="https_proxy=http://theproxy.com"
-
@stacksofplates Thank you very much It works.
-
@devops1 said in Kubernetes (Kubespray) Issue.:
@stacksofplates Thank you very much It works.
No problem!