Can you check the kubelet log on your minions? Seems the container failed
to start, there might be something wrong for your minions node. Thanks.
2015-02-22 15:08 GMT+08:00 Hongbin Lu hongbin...@gmail.com:
Hi all,
I tried to go through the new redis example at the quickstart guide [1],
but
Thanks Jay,
I checked the kubelet log. There are a lot of Watch closed error like
below. Here is the full log http://fpaste.org/188964/46261561/ .
*Status:Failure, Message:unexpected end of JSON input, Reason:*
*Status:Failure, Message:501: All the given peers are not reachable*
Please note
Hi Jay,
I tried the native k8s commands (in a fresh bay):
*kubectl create -s http://192.168.1.249:8080 http://192.168.1.249:8080 -f
./redis-master.yaml*
*kubectl create -s http://192.168.1.249:8080 http://192.168.1.249:8080 -f
./redis-sentinel-service.yaml*
*kubectl create -s
I suspect that there are some error after the pod/services parsed, can you
please use the native k8s command have a try first then debug k8s api part
to check the difference of the original json file and the parsed json file?
Thanks!
kubectl create -f .json xxx
2015-02-23 1:40 GMT+08:00
Hi all,
I tried to go through the new redis example at the quickstart guide [1],
but was not able to go through. I was blocked by connecting to the redis
slave container:
*$ docker exec -i -t $REDIS_ID redis-cli*
*Could not connect to Redis at 127.0.0.1:6379 http://127.0.0.1:6379:
Connection
