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/Docker.app/Contents/Resources/cli-plugins

> brew cleanup


Try installing hyperkit again,


> brew install hyperkit

It should be installed without any issue now.


NOTE - for MAC M1/M2 - Hyperkit will not work so install qemu


> brew install qemu


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

Client:

 Context:    default

 Debug Mode: false


Server:

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 -


With Hyperkit


minikube start --driver=hyperkit --container-runtime=docker

With qemu



minikube start --driver=qemu --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

Client:

 Context:    default

 Debug Mode: false


Server:

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

Client:
Context:    default
Debug Mode: false
Server:
 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!!

Comments

Popular posts from this blog

AJAX Progrraming

Ajax , shorthand for Asynchronous JavaScript and XML , is a web development technique for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user requests a change. This is meant to increase the web page's interactivity, speed, and usability. The Ajax technique uses a combination of: XHTML (or HTML) and CSS, for marking up and styling information. The DOM accessed with a client-side scripting language, especially JavaScript and JScript, to dynamically display and interact with the information presented. The XMLHttpRequest object is used to exchange data asynchronously with the web server. In some Ajax frameworks and in certain situations, an IFrame object is used instead of the XMLHttpRequest object to exchange data with the web server, and in other implementations, dynamically added tags may be used. ...

Nutch crawler and integration with Solr

Before moving ahead with this article, I assume you have Solr installed and running. If you would like to install Solr on windows, mac or via docker, please read Setup a Solr instance . There are several ways to install nutch which you can read from Nutch tutorial , however I have written this article for those who would like to install nutch using docker. I tried finding help on google but could not find any help for nutch installation using docker and spent good amount of time fixing issues specific to it. Therefore I have written this article to help and save time of other developers. Install nutch using docker- 1. Pull docker image of nutch using below command,      > docker pull apache/nutch 2. Once image is pulled, run the container,      > docker run -t -i -d --name nutchcontainer apache/nutch /bin/bash 3. You should be able to enter in the container and see bash prompt,      > bash-5.1#  Let's setup few important setting...

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

Could not load file or assembly 'Microsoft.Web.Infrastructure, Version=1.0.0.0, 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!!