Not able to configure Kubectl. #886
Comments
How about removing the lock file first? |
Tried moving the file - but the error is a secondary exception - because kubeconfig.lock is either a transient file during the transaction or it does not exist obrienbiometrics:single-node michaelobrien$ kubectl config use-context vagrant-single obrienbiometrics:single-node michaelobrien$ pwd |
The fix is actually to wait until the VM is fully initialized obrienbiometrics:single-node michaelobrien$ kubectl config use-context vagrant-single |
I refered https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant-single.html
I am not able to configure kubectl.
Use a custom KUBECONFIG path
$ kubectl config use-context vagrant-single
error: open /Users/vmudigal/coreos-kubernetes/single-node/kubeconfig.lock: file exists
vmudigal$ kubectl version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:44:38Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"darwin/amd64"}
The connection to the server 172.17.4.99:443 was refused - did you specify the right host or port?
The text was updated successfully, but these errors were encountered: