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.


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


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

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

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!!

Create chatbot in 20 minutes using RASA

This blog will help you create a working chatbot with in 20 minutes. For creating chatbot we need following libraries to be installed- >> Python3 >> Pip3 >> Rasa Lets start installing all libraries & dependencies which are need for creating chatbot. Note: I have used MAC, therefore sharing commands related to it. You can install it on Windows, Linux or any other operating system using respective commands. 1. Install Python3 > brew install python3 > python --version #make sure you have python3 installed 2. Install Pip3 > curl -O https://bootstrap.pypa.io/get-pip.py > sudo python3 get-pip.py If you get issue related to Frameoworks while installing pip, follow below steps -  > cd /usr/local/lib > mkdir Frameworks > sudo chown -R $(whoami) $(brew --prefix)/* Once installed check pip3 version > pip3 --version After python3 and pip3 is succeffully installed, proceed to next steps. 3. Install Rasa > pip

Running dotnet on Linux

Server: Linux, version SUSE 12 To run dotnet code on Linux, the first and foremost task is to "Install Mono package on linux". Note: Mono is an open implementation of Microsoft's .Net framework, including compilers. It uses the same development libraries on Linux which are being used on Windows. Therefore, if you code and compiled some mono code on Linux,  it will work for Windows as well.       zypper is a package installation tool which is used in this scenario. If zypper is not available, check which package manager tool is installed on server. Furthermore, to verify if zypper is installed or not, type zypper on command line which will show all options if zypper is available on server else it will show 'command not found'. zypper ar -r http://download.opensuse.org/repositories/Mono/SLE_11_SP2/Mono.repo The above command will download from mentioned URL in a new repository. Here 'ar' stands for 'add repo'. After adding it to repos