Kubernetes (Kubespray) Issue.

DustinB3403

@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 ?

flaxking

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.24

Are you behind a proxy? I think that's the common issue for people who experience this error.

devops1

@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.

devops1

@flaxking So, If I am behind the proxy how to solve this error? Pulling the docker image directly will knock out this error?

flaxking

@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

flaxking

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.

devops1

@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 ?

devops1

@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?

stacksofplates

@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"

devops1

@stacksofplates Thank you very much It works.

stacksofplates

@devops1 said in Kubernetes (Kubespray) Issue.:

@stacksofplates Thank you very much It works.

No problem!