This is the fine granular approach to install only the tools you need, but still using the choco install experience. That's why I started with the Choco packages for docker-machine, helped maintaining the docker-compose package and added some Docker Machine drivers as Chocolatey packages docker-machine-vmwareworkstation and docker-machine-vmware as well. I knew that there is a tool called docker-machine to create Linux VM's with the boot2docker.iso file.

I worked with VMware Workstation for years so the Docker Toolbox wasn't my thing.

Running VirtualBox VM's for other tasks that prevent the installation of Hyper-V.

Running a Windows 10 Home or LTSB version which is too old.

This package is usable for people that cannot run the newer Docker Desktop product. Manuel Riezebosch started a Chocolatey package docker-toolbox for it and still maintains it. created Docker Toolbox to have all tools and also VirtualBox bundled together. We're in discussion with the Chocolatey team how to softly fix this and transfer the Docker CLI into a new package name called docker-cli to make it more clear. Nowadays it might be confusing if people want to run choco install docker and 'just' get the Docker CLI without any Docker Engine. This package was and still is called docker. Ahmet Alp Balkan working at Microsoft at that time ported the Docker CLI to Windows so we had the docker.exe to communicate with remote Docker engines running in a Linux machine.

The first Docker tool that landed as a Chocolatey package was the Docker CLI. I'll give you a little bit of history and explain why they all exist in the following chapters. The following diagram shows you the most relevant Chocolatey packages for Docker. In these five years I went through several Windows machines and contributed missing Choco packages also for installing the Docker tools I needed. So I wrote my first Chocolatey package which is very easy as it only links to the official download URL's from the software vendor. This also lead me to contribute back to the Chocolatey community repository, because I just couldn't cinst packer at that time.

Since then I started with automation tools like Packer and Vagrant to describe repeatable development and test environments. This opened my eyes, wow there is a package manager for Windows. Did you remember how we have set up our dev machines a few years ago? Well, about five years ago I found this blog post by security expert Troy Hunt and his 102 simple steps for installing and configuring a new Windows 8 machine showed most of the time cinst this and cinst that. When I'm working with Windows I love to have a standarized way to install software.

How to uninstall docker toolbox