[Solved] Unable to start VM: create: precreate: exec: "docker": executable file not found in $PATH

Error:-
Unable to start VM: create: precreate: exec: "docker": executable file not found in $PATH

Occurence:- 
Occured during the minikube installation

Resolution:-
Docker was not installed on the vm so installed the docker using the get.docker.com script as
 curl -fsSL https://get.docker.com/ | sh  
This should automatically detect the operating system and install the docker on your system.

Comments

Post a Comment

Popular posts from this blog

[Solved] calico/node is not ready: BIRD is not ready: BGP not established (Calico 3.6 / k8s 1.14.1)

  Issue:-  The Issue was first recognised after we expose a service using the Nodeport and tried to access over the localhost on other node followed by Nodeport number. But the curl request failed with timeout On Inspecting the containers of the master node one of the containers of the calico node was not ready. When I used the describe container for that service it gave the error mentioned below. Error:-    Normal   Created    14m                kubelet            Created container calico-node   Normal   Started    14m                kubelet            Started container calico-node   Warning  Unhealthy  14m (x3 over 14m)  kubelet            Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable...
Read more

[Resolved] groupVersion shouldn't be empty

  Issue:-  When creating the simple resource like pod, replicaset, deployments etc got a groupVersion error specified below.  Error:-   groupVersion shouldn't be empty Effect:- Not able to create the resource because of the above error apiversion: v1 kind: Pod metadata: name: pod2 spec: containers: - name: c1 image: nginx Resolution:- If you look at the above configuration precisely you will find the  apiversion   has been specified incorrectly. It should have been  apiVersion   k.So just a difference of block letter can make that error. The same error will occur even if you forgot to mention the apiVersion in the configuration or it is misspelled. Below configuration will work fine. apiVersion: v1 kind: Pod metadata: name: pod2 spec: containers: - name: c1 image: nginx   Explanation:- apiVersion is hardcoded in the kubernetes. So if you misspell it, not use it or make a e...
Read more

[Solved] Gitlab remote: ERROR: Your SSH key has expired.

  Error:- We have been using Gitlab and recently I got the following error while pushing my change to the Gitlab Repository remote: remote: ======================================================================== remote: remote: ERROR: Your SSH key has expired. remote: remote: ======================================================================== remote: fatal: Could not read from remote repository. Cause:- The reason for this failure was that i created a ssh key about a year ago and gitlab by default puts a security policy that your ssh key will get expire after 1 year. This is something built in to improve security in Gitlab now because that timeperiod has elapsed of 1 year thats why it gives that error of ssh key has expired.
Read more