Recently I have been watching a tutorial where, in order to follow it, you need to have Docker running on your machine. So far, so good. But it turns out that the latest versions of Docker require Windows 10 Pro, Enterprise, or Education.
Which means that if you are like me and have just Windows 10 Home edition on your personal laptop, then you cannot use Docker… or maybe you still can.
First, let's do a short summary of the situation. What do we want to achieve and what do we currently have? We have Windows 10 OS Home edition on our machine. We would like to have Docker running on the same machine so that we are able to create docker images, run containers, and learn better and grow faster! The last one is a bit out of the scope of this article, but we should start from somewhere, no?
After defining what we want, let's see how to achieve it. Here are the steps I followed. It worked for me, which make me want to share it with you. And maybe I can save someone a few days of going back and forth to StackOverflow! After some reading, I found this article. It explains that it is possible to use Docker in Windows 10 Home by leveraging a Linux virtual machine and having Docker containers running on it.
Let's see how it works. It gives you the ability to have multiple virtual machines installed on your physical one. This way we can have a virtual machine which will be running Linux where our Docker will live. Then use Windows PowerShall and Chocolatey , your Windows package manager, to install a docker-machine by running the following:.
Next, we need to configure which ports are exposed when running Docker containers. This was the most critical detail that I forgot. We need to allow Docker to mount volumes located on your hard drive.
If you don't mind to use the default settings, do not forget to put your project under the 'Users' directory, e. In my case, I forgot about this and had to spend few days of head banging until I figured out why the heck was I getting a "Couldn't find package. Windows 10 bit: Pro build or higher, or Enterprise or Education build or higher. The following hardware prerequisites are required to successfully run Client Hyper-V on Windows Containers and images created with Docker Desktop are shared between all user accounts on machines where it is installed.
This is because all Windows accounts use the same VM to build and run containers. Note that it is not possible to share containers and images between user accounts when using the Docker Desktop WSL 2 backend.
Nested virtualization scenarios, such as running Docker Desktop on a VMWare or Parallels instance might work, but there are no guarantees. For more information, see Running Docker Desktop in nested virtualization scenarios. It typically downloads to your Downloads folder, or you can run it from the recent downloads bar at the bottom of your web browser. Follow the instructions on the installation wizard to authorize the installer and proceed with the install. When the installation is successful, click Close to complete the installation process.
If your admin account is different to your user account, you must add the user to the docker-users group. Right-click to add the user to the group. Log out and log back in for the changes to take effect. Docker Desktop does not start automatically after installation.
When the whale icon in the status bar stays steady, Docker Desktop is up-and-running, and is accessible from any terminal window. If the whale icon is hidden in the Notifications area, click the up arrow on the taskbar to show it. To learn more, see Docker Settings. When the initialization is complete, Docker Desktop launches the onboarding tutorial.
The tutorial includes a simple exercise to build an example Docker image, run it as a container, push and save the image to Docker Hub. If you would like to rerun the tutorial, go to the Docker Desktop menu and select Learn. Starting with Docker Desktop 3. When an update is available, Docker Desktop displays an icon to indicate the availability of a newer version.
