Skip to main content

Bye Bye Docker Desktop, Welcome Docker CLI

We are using docker desktop which has been licensed and this is really annoying for all developers. Good news is that, there is way to get rid of docker desktop and continue doing our great engineering work with docker CLI.

Here is the step by step guide to install Docker CLI on MAC -

Uninstall Docker Desktop

> brew uninstall docker

Also check Docker Desktop is removed from MAC as well. If not, delete the Docker desktop app from Applications folder.  

Install Hyperkit

> brew install hyperkit

If you are receiving any issue while installing hyperkit like below, it is because, sometime deletion of docker gives error, if it is not able to find the required folder. 

Error: Permission denied
@ apply2files - /usr/local/lib/docker/cli-plugins

Lets fix this issue by creating the folder once and running cleanup command - 

mkdir -p /Applications/

> brew cleanup

Try installing hyperkit again,

> brew install hyperkit

It should be installed without any issue now.

Install Docker CLI

> brew install docker

This will install docker CLI but not docker deamon(dockerd). You may check it by running 'docker info' command.

docker info


 Context:    default

 Debug Mode: false


ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Install Kubectl

> brew install kubectl

If its already installed, run

> brew reinstall kubectl

Install Minikube

> brew install minikube

If its already installed, run

> brew reinstall minikube

If you get below warning, run 'brew link minikube'

Warning: minikube 1.24.0 is already installed, it's just not linked.

To link this version, run:

brew link minikube

> brew link minikube

If you still get any warning or exception like below, run 'brew link --overwrite minikube'

Linking /usr/local/Cellar/minikube/1.24.0...

Error: Could not symlink bin/minikube

Target /usr/local/bin/minikube

already exists. You may want to remove it:

  rm '/usr/local/bin/minikube'

> brew link --overwrite minikube

Finally start the Kubernetes cluster

minikube start --kubernetes-version=v1.19.14 --driver=hyperkit --container-runtime=docker

If you receive below error while running the command, run 'minikube delete' and start 'minikube start --kubernetes-version=v1.19.14 --driver=hyperkit --container-runtime=docker' again.

minikube v1.24.0 on Darwin 11.6.2

❗  Deleting existing cluster minikube with different driver docker due to --delete-on-failure flag set by the user.

💢  Exiting due to GUEST_DRIVER_MISMATCH: The existing "minikube" cluster was created using the "docker" driver, which is incompatible with requested "hyperkit" driver.

💡  Suggestion: Delete the existing 'minikube' cluster using: 'minikube delete', or start the existing 'minikube' cluster using: 'minikube start --driver=docker'

> minikube delete

> minikube start --kubernetes-version=v1.19.14 --driver=hyperkit --container-runtime=docker

It may ask for password for sudo permissions, please provide and install required packages. 

Kubectl is configured now. 

Check 'docker info'

docker info


 Context:    default

 Debug Mode: false


ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Set the environment variable(# Tell Docker CLI to talk to minikube's VM)

eval $(minikube docker-env)

Now run 'docker info', it should start docker deamon - 

docker info

Context:    default
Debug Mode: false
 Containers: 14
 Running: 14
 Paused: 0
 Stopped: 0
 Images: 10
 Server Version: 20.10.8
Now run 'docker info', it should start docker deamon - 

Happy coding!!


Popular posts from this blog

Cannot alter the login 'sa', because it does not exist or you do not have permission.

Working on projects, it can happen that 'sa' account gets locked. If it is on local machine OR development boxes, onus would be on you to fix it. If scripts and SQL steps are not working, this might help you fixing the issue. Steps to unlock 'sa' account and resetting the password. 1. Open SQL Server Configuration Manager 2. Select SQL Server Services -> 'SQL Server' service. 3. Right click on 'SQL Server' service and click on "Startup Parameters". For 2008, server "Startup Parameters" are inside Advanced tab.   4. Add '-m' in startup parameters as shown above and click on 'Add'. This will put SQL server into 'Single User Mode' and local admin will have 'Super User' rights. For 2008, server you have to add ':-m' in the last of the existing query. 5. Save the settings and Restart the service. 6. Now open the SQL Server Management Studio and connect to database using 'Windows A

Could not load file or assembly 'Microsoft.Web.Infrastructure'

Could not load file or assembly 'Microsoft.Web.Infrastructure, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. What 'Micorosoft.Web.Infrastructure' does? This dll lets HTTP modules register at run time. Solution to above problem: Copy 'Micorosoft.Web.Infrastructure' dll in bin folder of your project and this problem should be resolved. If you have .Net framework installed on machine, this dll should be present on it. You can search for this dll and copy it in your active project folder.   Alternatively,  you can install this dll using nuget package manager PM> Install-Package Microsoft.Web.Infrastructure -Version 1.0.0 Happy coding!!

Git merge from one repo to another repo

This blog is for those who are looking for merging code from one repo to another repo. Why I will merge code from one repo to another? I forked from one git repo( may be some public git repo ) and did some cutomization on existing code. Occasionaly, features are being introduced in main git branch and I would like to get all those features in my own git repo. In this scenario, I would like to merge latest changes in my git repo. Here are few simple steps which will merge code from one git repo to another- 1. Clone the repo1(source git repo) > git clone   > git pull 2. Clone the repo2(destination git repo) > git clone > git pull 3. Goto repo2 (destination git folder) and checkout your prefered branch > cd repo2 > git checkout master>  4. Use below command to see the remote branch associated with your destination git repo > git remote -v  origin