vyshane / docker-compose-kubernetes Goto Github PK

Running ./kube-up-docker-machine.sh sets up the VM and such, but gets stuck at Waiting for Kubernetes cluster to become available...

$ ./kube-up-docker-machine.sh
kubernetes_skydns_1 is up-to-date
kubernetes_master_1 is up-to-date
kubernetes_kube2sky_1 is up-to-date
kubernetes_etcd_1 is up-to-date
kubernetes_proxy_1 is up-to-date
Waiting for Kubernetes cluster to become available...

Looks like the underlying cause may be that kubectl isn't found on my mac. Should that command be available at this step?

Hi,

On MAC OSX (with boot2docker), my docker and docker-machine are getting slow when my kubernetes cluster is up, after a while I get some timeout and then it doesn't work at all while kubectl still works fine.
Did you note this or is it just me ? Maybe you don't have this issue if you are using linux.

Please share your experience.

Arnaud.

This makes the
dns_host=$(echo $DOCKER_HOST | awk -F'[/:]' '{print $4}')
in activate-dns.sh an empty string, ultimately leading to the error:
The Endpoints "kube-dns" is invalid:subsets[0].addresses[0].ip: invalid value '': invalid IPv4 address

In that case, should it be replaced by 127.0.0.1 ? (that's what fixed it for me)

Would be great to have kube-ui in the docker-compse yaml. :-)

Good job with this docker-compose

Here's a simple way to see the issue:

1. Use the kube-up.sh script to set up kubernetes.
2. Follow http://kubernetes.io/v1.1/docs/user-guide/secrets/README.html to create a secret and a pod that consumes it.
3. After creating the pod (and waiting some time for the wheels to spin), use kubectl describe pods/secret-test-pod to list the pod's events.

You will see events like these:

FailedSync   Error syncing pod, skipping: IsLikelyNotMountPoint("/var/lib/kubelet/pods/8c8d900f-992c-11e5-836b-46ca7ac5766f/volumes/kubernetes.io~secret/secret-volume"): file does not exist
FailedMount  Unable to mount volumes for pod "secret-test-pod_default": IsLikelyNotMountPoint("/var/lib/kubelet/pods/8c8d900f-992c-11e5-836b-46ca7ac5766f/volumes/kubernetes.io~secret/secret-volume"): file does not exist

And the pod will never make it out of the "Pending" state.

Hi,

I end up with such error:

$ ./kube-up.sh 
WARNING: devicemapper: usage of loopback devices is strongly discouraged for production use.
         Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
WARNING: No swap limit support
kubernetes_proxy_1 is up-to-date
kubernetes_etcd_1 is up-to-date
kubernetes_master_1 is up-to-date
kubernetes_skydns_1 is up-to-date
kubernetes_kube2sky_1 is up-to-date
Waiting for Kubernetes cluster to become available...
Kubernetes cluster is up.
W1221 17:06:47.077436   29898 factory_object_mapping.go:423] Failed to download OpenAPI (Get http://10.192.0.2:8080/swagger-2.0.0.pb-v1: dial tcp 10.192.0.2:8080: getsockopt: no route to host), falling back to swagger
Unable to connect to the server: dial tcp 10.192.0.2:8080: getsockopt: no route to host

Any idea why?

Hi,

Something that caught my eye is that this setup does not create a token for the default service account. Have you experienced the same problem? and if so, how did you fix it?

I'm trying to connect a pod to the API master without going through the Insecure option.

Cheers,
Leo.-

When following Kubernetes documentation (https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/dns) on how to test the DNS resolution:

kubectl exec busybox -- nslookup kubernetes.default

The resolution fails. But if we change kubernetes.default to the fully qualified name:

kubectl exec busybox -- nslookup kubernetes.default.svc.cluster.local

The resolution succeeds.

We should keep external dependencies to a minimum. Kubernetes addons like DNS and kube-ui are launched using Kubernetes itself, and docker run is sufficient for bringing up the base Kubernetes system.

Getting "Unsupported config option for master service: 'pid' when i am trying to setup on Ubuntu 14.04

I run docker-composer-kubernetes on Linux without $DOCKER_HOST assigned, so it set DNS ENDPOIT to 127.0.0.1. However, in kubernetes the loopback IP can not be used as Endpoint IP(*), so I get error:

subsets[0].addresses[0].ip: invalid value '127.0.0.1', Details: may not be in the loopback range (127.0.0.0/8)

*) https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/services.md