![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |