{"id":2075,"date":"2021-10-03T15:46:40","date_gmt":"2021-10-03T19:46:40","guid":{"rendered":"https:\/\/www.alpharithms.com\/?p=2075"},"modified":"2021-10-03T15:48:41","modified_gmt":"2021-10-03T19:48:41","slug":"installing-docker-on-windows","status":"publish","type":"post","link":"https:\/\/www.alpharithms.com\/installing-docker-on-windows-404615\/","title":{"rendered":"Installing Docker on Windows: Navigating Common Config Issues"},"content":{"rendered":"

Docker is a technology that allows developers to deploy applications across a much wider range of systems. It does this by “containerizing” certain hardware and software features so developers can deploy applications to more predictable software environments.<\/p>\n

Installing Docker for Windows is a breeze\u2014made possible by a Windows-based installer provided, for free, by Docker. This quick tutorial is meant to serve as a brief\u00a0practical<\/em> guide to installing Docker on a Windows 10 machine\u2014refer to the documentation for complete guidance.<\/p>\n

Initial Download and Install<\/h2>\n

The first step is to download Docker’s installation manager<\/a>. This software will launch and install the Docker software on your local machine. After the software has finished installing you will be prompted with a standard license and terms page:<\/p>\n

\"docker<\/p>\n

After accepting the terms, Docker will launch for the first time. This can be a seamless process, or\u2014in such cases that were the inspiration for this post\u2014one riddled with warnings, exceptions, and necessary reboots. For example, one might see a screen such as this the first time attempting to boot Docker after install:<\/p>\n

\"docker
This warning indicates that the system’s BIOS needs to enable hardware virtualization.<\/figcaption><\/figure>\n

This is a common error when getting started with virtualization applications and, in most cases, can be remedied. One need only to reboot, hit F2<\/code> and\/or DEL<\/code> to enter BIOS (on most systems), and then find the proper option to enable hardware virtualization.\u00a0 There are other errors that may occur during the initial launch of Docker and the remainder of this post will cover the most common.<\/p>\n

Enabling Virtual Machine Platform<\/h2>\n

Windows VMP allows the system to allocate more compute resources for virtualized environments. There are two steps to fully enabling this service to allow for Docker to run.<\/p>\n

    \n
  1. Enable the Virtual Machine Platform option in the Turn Windows Features On\/Off section;<\/li>\n
  2. Enable Hardware Virtualization via your Mother Board’s BIOS menu. Note that this process will differ based on your system’s motherboard.<\/li>\n<\/ol>\n

    Enabling Window Virtual Machine Platform<\/h3>\n

    The Windows Virtual Machine Platform can be enabled by typing Turn Windows Features On or Off into the search box on the Windows Task Bar (look for the option to pop up after the first word is typed.) You should see something like this image:<\/p>\n

    \"turn
    Click the topmost option labeled Turn windows services on or off.<\/figcaption><\/figure>\n

    After clicking that menu option you will then see the following screen pop up:<\/p>\n

    \"virtual
    Check that the options for Virtual Machine Platform, Windows Subsystem for Linux, and Hyper-V are checked here.<\/figcaption><\/figure>\n

    Both the Virtual Machine Platform and Windows Subsystem for Linux options need to be enabled for Docker to run on Windows. Ensure the dialog box on your machine reflects that shown in the image above before proceeding.<\/p>\n

    Enabling Hardware Virtualization via BIOS<\/h3>\n

    There are countless ways to do this depending on the motherboard your system is running and possibly even the firmware version that board is running. This post cannot, nor will it attempt to, cover even half of the possible configuration options out there.<\/p>\n

    As a\u00a0single<\/em> example, however\u2014for an MSI-based board\u2014one need only “enable” the SVM option in BIOS, as explained here<\/a>. \u00a0For a more general discussion on hardware virtualization, check out this resource<\/a> by the University of Berkley.<\/p>\n

    Enabling Hyper-V<\/h3>\n

    In some cases, Docker may not function properly without Windows 10’s Hyper-V service enabled. This is an optional feature that is bundled with Windows and thus requires no additional downloads. Read the documentation here<\/a>. If Docker still throws an error after enabling the WSL and VMP this option will need to be enabled.<\/p>\n

    Installing Linux Subsystem for Windows<\/h2>\n

    Since 2017 Windows has allowed users to install a Linux-based OS<\/a> as a “subsystem” in the normal Windows 10 environment. This is known as the Windows Subsystem for Linux (WSL). The initial implementation (WSL1) wasn’t a full-fledged distribution of Linux and had many drawbacks.<\/p>\n

    Since Version 1903 (~May 2020) Windows now supports WSL2 which offers a more robust Linux environment featuring the full Linux kernel. Read more about WSL1 vs. WSL2 here<\/a>. One drawback of WSL\u2014in terms of software compatibility\u2014is that it requires a virtualization engine known as Hyper-V to be present, and running.<\/p>\n

    This virtualized the Linux Kernel and allows a fuller-featured Linux experience in a Windows environment. However, this initially made it impossible for other virtualization solutions like VMware or Oracle’s VirtualBox to run. However, those issues have reportedly been fixed for both VMware<\/a> and VirtualBox<\/a>.<\/p>\n

    Installing<\/h3>\n

    Run the following command: wsl --install<\/code>. If WSL is already installed on your system this won’t accomplish very much. If not, however, buckle up for a bit of a process. If WSL2 is already installed, but possibly out-of-date, you may receive a Docker.ApiServices.WSL2.WslKernelUpdateNotInstalledException<\/code> message when Docker starts up, something like this:<\/p>\n

    \"wsl
    The WSL2 Kernel may need updating before Docker is able to run on the Windows 10 environment, even with WSL enabled.<\/figcaption><\/figure>\n

    If you are receiving a\u00a0 then you have the WSL2 subsystem installed and only need to update via the wsl --update<\/code> command. This will produce the following output (as of 10\/2021):<\/p>\n

    C:\\Windows\\system32>wsl --update\r\nChecking for updates...\r\nDownloading updates...\r\nInstalling updates...\r\nThis change will take effect on the next full restart of WSL. To force a restart, please run 'wsl --shutdown'.\r\nKernel version: 5.10.16<\/pre>\n
    To avoid rebooting the entire system, you can simply run the wsl --shutdown<\/code> command and then follow up with the wsl<\/code> command (all in the same terminal session.) This will result in a new instance of the Linux Subsystem.<\/p>\n
    Note<\/strong>: If you get a message that wsl isn’t a valid command that means you are already\u00a0in\u00a0<\/em>the WSL system! WSL is a Windows-recognized command.<\/p>\n
    Update Apps<\/h3>\n
    Linux provides a convenient way for users to be notified of and install updates to their system applications. The apt update<\/code> and apt install<\/code> commands will, in order, fetch a list of apps that have possible upgrades and then install those upgrades to the system.<\/p>\n
    While updating the WSL system one might as well update other applications as well\u2014why not, right? Read more about the inner workings of apt-update<\/code> and apt-upgrade<\/code> here. If you received a WslKernelUpdateNotInstalledException<\/code> earlier chances are your system will benefit greatly from updating applications.<\/p>\n
    Re-Launch Docker<\/h2>\n
    Docker should now be ready to launch after enabling the Windows Virtual Machine platform, installing and ensuring WSL is up-to-date, and ensuring hardware virtualization is enabled in BIOS. Assuming all has gone according to plan, you should now see the following screen when launching Docker:<\/p>\n
    \"Docker
    The welcome screen indicating a successful installation of Docker on Windows 10<\/figcaption><\/figure>\n
    Further Reading<\/h2>\n
    This article is meant to outline only the common steps and issues related to installing Docker on a Windows 10 Machine. For more information on the WSL system, its initial installation, and performance benefits vs. the WSL1 system, read Microsoft’s Comparing WSL 1 and WSL 2<\/em><\/a> post in their documentation and the Microsoft documentation for installing WSL<\/a>.<\/p>\n
    Final Thoughts<\/h2>\n
    Docker is a power virtualization tool that is utilized by developers around the world. Its ability to provide a wider range of software and hardware support helps make deploying applications\u2014especially cloud-based applications\u2014much less technical and frustrating. At the\u00a0very<\/em> least, it allows developers and businesses to be more selective regarding services such as hosting, storage, and database management.<\/p>\n
    Installing Docker on Windows is a straightforward process but, like anything software-related, is prone to some bugs. The issues described in this article are some of the common issues one might face during installation. If you are aware of any other common problems please don’t hesitate to reach out<\/a> and describe them and have them considered for inclusion here.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Docker is a technology that allows developers to deploy applications across a much wider range of systems. It does this by “containerizing” certain hardware and software features so developers can deploy applications to more predictable software environments. Installing Docker for Windows is a breeze\u2014made possible by a Windows-based installer provided, for free, by Docker. This […]<\/p>\n","protected":false},"author":2,"featured_media":2085,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[10],"tags":[554,550,555,551,553,552],"acf":[],"_links":{"self":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/2075"}],"collection":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/comments?post=2075"}],"version-history":[{"count":4,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/2075\/revisions"}],"predecessor-version":[{"id":2088,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/posts\/2075\/revisions\/2088"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/media\/2085"}],"wp:attachment":[{"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/media?parent=2075"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/categories?post=2075"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.alpharithms.com\/wp-json\/wp\/v2\/tags?post=2075"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}