Have you previously installed Docker Toolbox, Docker Machine, or VirtualBox?
- How To Run Docker On Windows 10 Home
- Will Docker Run On Windows 10 Home
- How To Run Docker On Windows 10 Home Edition
Docker for Windows now requires Microsoft’s Hyper-V. Once enabled, VirtualBox will no longer be able to run virtual machines (your VM images will still remain). You can still use
docker-machine to manage remote hosts.
You have the option to import the
default VM after installing Docker for Windows from the Settings menu in the System Tray.
Running Docker containers on a Windows 10 PC has been difficult for the last few years. It’s even more difficult if you want to run VirtualBox virtual machines (VM) at the same time. A casual Google search will turn up droves of postings saying that you absolutely can not do both at once. To run Docker on Windows 10 Home Edition you need to do two things: 1. Check if the Hardware Virtualization is Enabled 2. Install Docker Toolbox instead of Docker Desktop Full Guide.
Docker for Windows enables Hyper-V if necessary; this requires a reboot.
Docker for Windows runs on 64-bit Windows 10 Pro, Enterprise, and Education; 1511 November update, Build 10586 or later. Docker plans to support more versions of Windows 10 in the future.
- Download Docker.
InstallDocker.msito run the installer.
- Follow the Install Wizard: accept the license, authorize the installer, and proceed with the install.
- Click Finish to launch Docker.
- Docker starts automatically.
- Docker loads a “Welcome” window giving you tips and access to the Docker documentation.
The whale in the status bar indicates a running (and accessible via terminal) Docker instance.
Open PowerShell or your favorite Windows terminal (e.g., Command prompt) and enter
docker run hello-world.
Windows prompts you for access every time Docker starts, allowing Docker to manage the Hyper-V VM’s. The first time Docker starts, you may need to provide the token from the Beta invitation email. When initialization completes, select About Docker from the notification area and verify you have the latest version.
From PowerShell (or your favorite Windows terminal), check the versions of
docker-compose, and verify your installation:
How To Run Docker On Windows 10 Home
Before you stop, let’s test a Dockerized webserver; from PowerShell or cmd.exe, run:
If your host does not already have it, Docker downloads
nginx from Docker Hub and starts it. As soon as the download completes, point your web browser to http://docker to view the start page. You should see:
Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
For online documentation and support please refer to nginx.org.Commercial support is available at nginx.com.
Thank you for using nginx.
If your CPU does not support virtualization, or if you do not have a 64-bit CPU, you cannot run Docker locally.
If you do not run a 64-bit version of Windows Windows 10 Pro, Enterprise, or Education; 1511 November update, Build 10586 or later, you cannot run Docker for Windows.
You can install Docker Toolbox if you have a 64-bit version of Windows 7 or later. Alternately, you do have the option to upgrade.
Next: Install Docker on Linux
Requirements and things to know before installing Docker for Linux.
This topic describes how to run your first Windows container, after setting up your environment as described in Get started: Prep Windows for containers. To run a container, you first install a base image, which provides a foundational layer of operating system services to your container. Then you create and run a container image, which is based upon the base image. For details, read on.
Install a container base image
All containers are created from container images. Microsoft offers several starter images, called base images, to choose from (for more details, see Container base images). This procedures pulls (downloads and installs) the lightweight Nano Server base image.
Open a command prompt window (such as the built-in command prompt, PowerShell, or Windows Terminal), and then run the following command to download and install the base image:
If you see an error message that says
no matching manifest for unknown in the manifest list entries, make sure Docker isn't configured to run Linux containers.
After the image is finished downloading—read the EULA while you wait—verify its existence on your system by querying your local docker image repository. Running the command
docker imagesreturns a list of installed images.
Here's an example of the output showing the Nano Server image.
Run a Windows container
For this simple example, a ‘Hello World’ container image will be created and deployed. For the best experience, run these commands in an elevated command prompt window (but don't use the Windows PowerShell ISE—it doesn't work for interactive sessions with containers, as the containers appear to hang).
Start a container with an interactive session from the
nanoserverimage by entering the following command in your command prompt window:
After the container is started, the command prompt window changes context to the container. Inside the container, we'll create a simple ‘Hello World’ text file and then exit the container by entering the following commands:
Get the container ID for the container you just exited by running the docker ps command:
Create a new ‘HelloWorld’ image that includes the changes in the first container you ran. To do so, run the docker commit command, replacing
<containerid>with the ID of your container:
When completed, you now have a custom image that contains the hello world script. This can be seen with the docker images command.
Here's an example of the output:
Finally, run the new container by using the docker run command with the
--rmparameter that automatically removes the container once the command line (cmd.exe) stops.
The result is that Docker created a container from the 'HelloWorld' image, Docker started an instance of cmd.exe in the container, and the cmd.exe read our file and output the contents to the shell. As the final step, Docker stopped and removed the container.
Run a Windows container using Windows Admin Center
You can use Windows Admin Center to run your containers locally. Specifically, you use the the Containers extension of your Windows Admin Center instance to run the containers. First, open the container host you want to manage, and in the Tools pane, select the Containers extension. Then, select the Images tab inside the Container extension under Container Host.
If your host doesn't have a base container image, select the Pull option to open the Pull Container Image settings:
In the Pull Container Image settings, provide the image URL and the tag. If you aren't certain which image to pull, Windows Admin Center provides a list of common images from Microsoft. You can also provide the credentials to pull an image from a private repository. Once you fill out the necessary information, click Pull. Windows Admin Center will start the pull process on the container host. After the download is complete, you should see the new image on the Images tab.
Select the image you want to run, and click Run.
Will Docker Run On Windows 10 Home
On the Run menu, set up the configuration for the container, such as the container name, the isolation type, which ports to publish, and memory and CPU allocation. Additionally, you can append Docker run commands that are not in the UI, such as -v for persistent volume. For more information on available Docker run parameters, review the documentation.
Once you have finished the configuration for the container, click Run. You can see the status of the running containers on the Containers tab: