| 2015-10-06 08:01:31 |
E Shijia |
description |
After creating a k8sbay and a pod for the redis-master as the dev-quickstart.rst, I found the status of the pod is always PENDING. Therefore, I accessed to the minon with , and ran the docker command:
sudo docker images
I could find the images was already downloaded.
To test whether the docker worked well, I just ran:
sudo docker run hello-world
At last, i got the message：
Post http:///var/run/docker.sock/v1.19/containers/55serwsvcbgydefcbfjeasdfdghadfaasdfhwfg...../start EOF. Are you trying to connect to a TLS-enabled daemon without TLS?
Typically, the TLS error will occur when we don't run the docker command with sudo. But why the error occurred in the k8sbay?
I was confused with that. I think it is the reason that why redis-master pod was always pending. |
After creating a k8sbay and a pod for the redis-master as the dev-quickstart.rst, I found the status of the pod is always PENDING. Therefore, I accessed to the minon with ssh, and ran the docker command:
sudo docker images
I could find the images was already downloaded.
To test whether the docker worked well, I just ran:
sudo docker run hello-world
At last, i got the message：
Post http:///var/run/docker.sock/v1.19/containers/55serwsvcbgydefcbfjeasdfdghadfaasdfhwfg...../start EOF. Are you trying to connect to a TLS-enabled daemon without TLS?
Typically, the TLS error will occur when we don't run the docker command with sudo. But why the error occurred in the k8sbay?
I was confused with that. I think it is the reason that why redis-master pod was always pending. |
|
