Closed huangsam closed 8 years ago
I got the same thing - which I found out because mattermost was failing, and I was trying to debug.
@huangsam @johnmark thanks for pointing this out - we'll let you know as soon as we start working on this bug. Should be in a few days.
My theory for the provided IP is already allocated
error is that at some point the DNS Service was successfully created leading to the IP conflict. The logic in dns.go attempts to create the Service in a loop regardless if it exists or not.
If this is the case then DNS+Services should work correctly. I'm looking into recreating this and attempting a fix.
In the meantime a way to check if this is caused by a Service already existing is to delete or rename the localkube data directory (by default it's ~/.localkube
). This will cause a fresh cluster to be started.
I was able to recreate the problem and create a patch that worked for me.
@huangsam & @johnmark: Can you docker pull redspreadapps/localkube:latest
and stop and start the cluster to confirm that this fixes it for you?
It works now - I still couldn't get mattermost working with localkube, but once I got past this error, I found the real issue: I hadn't set up SELinux properly :)
Thanks.
I first run the following commands in my Vagrant VM:
I run
docker logs localkube
and I notice that I encounter the kube-dns issue endlessly:Creating pods and accessing
kubectl cluster-info
works fine. Curling on port 8080 returns the api routes as well. However, my concern is that the interactions between services/pods will not work properly. Not sure if there's anything I can configure to resolve the kube-dns issues that I am encountering.I also found it interesting that the downloaded spread version was 0.0.3 and not 0.1.3.