» Docker » How to install Docker on Windows 10 without Hyper-V

How to install Docker on Windows 10 without Hyper-V

4 Mar
Posted on 87

Let me start by saying that it is quite hard to exactly understand the different Docker editions. Only this page is already confusing. There is a Community Edition (CE) and an Enterprise Edition (EE). But in the table there are three editions listed and none of them are named exactly the same as the names in the list. As far as I understand, the Docker Community is for free, while Docker Enterprise is the paid version.

And there is also something called Docker Engine – Community and Docker Engine – Enterprise. It seems like these are free versions, whereas the Community version for Windows 10 is also called Docker Desktop for Windows. Docker Desktop for Windows comes with an installation program and has a (basic) GUI. The version for Windows Server is Docker Engine – Enterprise and does not have a GUI nor an installation program.

Why do I start with this? Because both Docker Desktop for Windows and Docker Engine – Enterprise can be downloaded and installed for free. The Docker website does not mention any pricing for these products and the documentation makes clear how to install and does not talk about any license. I wanted to make clear that what I’m about to tell you is legal and not an infringement of any license terms.

What’s the point? Well, Docker Desktop for Windows requires Hyper-V to be enabled on your Windows 10 system, while Docker Engine – Enterprise (from now on referred to as Docker EE) does not. I was wondering if it would be possible and officially supported to install Docker EE on Windows 10. And it appears to be the case.

Why would I want that? Not because I have a problem with Hyper-V on itself. I’ve used it for many years to maintain different installations of Dynamics NAV. And even when Microsoft started to ship Dynamics NAV and Business Central as docker images, I used an Hyper-V VM with Docker installed instead of using Docker directly on my laptop. Just because Docker only supported containers in Hyper-V mode on Windows 10, which my laptop did not really like in combination with other native Hyper-V VM’s.

Since Docker supports process isolation on Windows 10 (starting with version 1809) it became time to say goodbye to my Hyper-V setup and switch to running containers directly on Windows 10. And because I didn’t need Hyper-V anymore, I also decided to get totally rid of it. That was wrong. Docker Desktop installed without complaining, but it didn’t want to start. Instead, I was presented with this screen:


And when I chose Cancel, I got this error message:

Too bad… even if you plan to not use Hyper-V based containers, you have to install Hyper-V otherwise Docker Desktop will not run after installation. I’ve heard it is because of Linux containers. They can only run inside an Hyper-V based container. And because Docker Desktop supports to switch between Windows and Linux containers, it simply expects you to have Hyper-V installed, no matter what.

Ok, but is that so bad after all? Well, maybe it is, maybe not. In my experience, Hyper-V can cause problems when combined with Docker running in process isolation mode. Especially networking seems to be quite vulnerable when Docker and Hyper-V have to work together with virtual networks.

Because Windows 10 and Windows Server share the same codebase, I was wondering if it would be possible to install Docker EE on Windows 10. Just like you install it on Windows Server. So I followed the instructions, but to no avail. I ran into another error:

Bummer…

Because I’m that kind of curious guy, I tried to find out the what this error is about. And you know what? It’s just a bug in the installation script. It’s not because Windows 10 is not supported with Docker EE. Just a bug in the script that could be solved a year ago. The script of DockerMsftProvider is available on GitHub. Make sure you are in the master branche, in case you take a look. The default development branche is already quite some commits behind master (sigh).

So, what’s the bug? There is a test on operating system, because it wants to run a different cmdlet when installing on Windows 10. It wants to test if the Windows feature Containers is installed.

And you know what? My system does not have ‘Microsoft Windows 10’ as output, but ‘Microsoft Windows 10 Pro‘. So the script fails, because it tries to run the cmdlet Get-WindowsFeature which is only available on Windows Server.

But wait… it gets worse. The suggestion in the script is that there is a difference between Windows 10 and Windows Server. Which is not true. The cmdlet Get-WindowsOptionalFeature works both on Windows Server and Windows 10! So why using the other cmdlet that is only supported on Windows Server? That’s a cmdlet you use when you want to work on a remote system. In this case that’s not what we do, so the solution here would be to just use Get-WindowsOptionalFeature (and a few lines later Enable-WindowsOptionalFeature). Without even testing on operating system, the script would be valid for both Windows 10 and Windows Server!

Of course I have made a bugfix, including some other small fixes, and created a pull request. The bad news is, there were already 5 pull request waiting, the oldest waiting for more than a year (and coincidentally for the very same bug, just a different solution). I wouldn’t be surprised if my pull request will be ignored as well.

So, what can we do to install Docker EE on Windows 10? Well, I have two options for you. Option number 1 is do a manual install, which is quite easy to do. Option number 2 is to download my version of the module DockerMsftProvider and let it install Docker for you.

Option 1: Manual install

The documentation of Docker EE contains a step-by-step instruction to use a script to install Docker EE. Follow that script and you will be safe. It can also be used to update Docker, just by downloading the latest files and overwrite the existing files.

Here is a modified version of that script. It will automatically detect the latest stable version, download and extract it and install it as a service.

# Install Windows feature containers
$restartNeeded = $false
if (!(Get-WindowsOptionalFeature -FeatureName containers -Online).State -eq 'Enabled') {
    $restartNeeded = (Enable-WindowsOptionalFeature -FeatureName containers -Online).RestartNeeded
}
if (Get-Service docker -ErrorAction SilentlyContinue)
{
    Stop-Service docker
}
# Download the zip file.
$json = Invoke-WebRequest https://dockermsft.azureedge.net/dockercontainer/DockerMsftIndex.json | ConvertFrom-Json
$stableversion = $json.channels.cs.alias
$version = $json.channels.$stableversion.version
$url = $json.versions.$version.url
$zipfile = Join-Path "$env:USERPROFILE\Downloads\" $json.versions.$version.url.Split('/')[-1]
Invoke-WebRequest -UseBasicparsing -Outfile $zipfile -Uri $url
# Extract the archive.
Expand-Archive $zipfile -DestinationPath $Env:ProgramFiles -Force
# Modify PATH to persist across sessions.
$newPath = [Environment]::GetEnvironmentVariable("PATH",[EnvironmentVariableTarget]::Machine) + ";$env:ProgramFiles\docker"
$splittedPath = $newPath -split ';'
$cleanedPath = $splittedPath | Sort-Object -Unique
$newPath = $cleanedPath -join ';'
[Environment]::SetEnvironmentVariable("PATH", $newPath, [EnvironmentVariableTarget]::Machine)
$env:path = $newPath
# Register the Docker daemon as a service.
if (!(Get-Service docker -ErrorAction SilentlyContinue)) {
  dockerd --exec-opt isolation=process --register-service
}
# Start the Docker service.
if ($restartNeeded) {
    Write-Host 'A restart is needed to finish the installation' -ForegroundColor Green
    If ((Read-Host 'Do you want to restart now? [Y/N]') -eq 'Y') {
      Restart-Computer
    }
} else {
    Start-Service docker
}

Run this script, and you will have Docker EE installed on Windows 10. Make sure to save the script and use it again to update to a newer version.

Option 2: Use DockerMsftProvider

If you want to use DockerMsftProvider with my fixes, then download the module from my GitHub repository and copy it to your PowerShell modules folder. I have create a little script that downloads the two files to the PowerShell modules folder and runs the script for you.

A smal note: while testing the script again, I noticed that the path variable was not updated. I guess it’s another bug, not sure about it. So you might want to go with option 1 anyway… 😉

$paths = $env:psmodulePath.Split(';')
$modulePath = Join-Path $paths[0] "DockerMsftProvider"
if (!(Test-Path $modulePath)) {
  New-Item -Path $modulePath -ItemType Directory
}
$outfile = Join-Path $modulePath 'DockerMsftProvider.psm1'
Invoke-WebRequest -UseBasicParsing -OutFile $outfile -Uri https://raw.githubusercontent.com/ajkauffmann/MicrosoftDockerProvider/master/DockerMsftProvider.psm1
$outfile = Join-Path $modulePath 'DockerMsftProvider.psd1'
Invoke-WebRequest -UseBasicParsing -OutFile $outfile https://raw.githubusercontent.com/ajkauffmann/MicrosoftDockerProvider/master/DockerMsftProvider.psd1
Install-Package Docker -ProviderName DockerMsftProvider -Force

And here you have Docker EE running on Windows Server 10.

Portainer

Another benefit of installing Docker EE is that Portainer works out of the box. You don’t need to do any settings, like exposing port 2375. The next two docker commands download and install Portainer for you.

docker pull portainer/portainer
docker run -d --restart always --name portainer --isolation process -h portainer -p 9000:9000 -v //./pipe/docker_engine://./pipe/docker_engine portainer/portainer

Open portainer with http://localhost:9000, provide a username and password and then click on Manage the local Docker environment. Click Connect to continue.

Then click on the local connection to manage your containers and images in a GUI.

That’s it! As you can see, it is perfectly possible to install and run Docker EE on Windows 10. For me this was really a set-and-forget installation.

Good luck!

Disclaimer: scripts are tested on my Windows 10 v1809 installation. No guarantee it will work on your installation. Scripts are provided ‘as-is’ and without any support. 😉

You may also like:

87 thoughts on “How to install Docker on Windows 10 without Hyper-V”

  1. I almost did the same,

    Invoke-WebRequest -UseBasicParsing -OutFile docker-18.09.0.zip https://download.docker.com/components/engine/windows-server/18.09/docker-18.09.0.zip
    Expand-Archive docker-18.09.0.zip -DestinationPath $Env:ProgramFiles -Force
    $null = Install-Package Docker -ProviderName DockerMsftProvider -Force
    dockerd –register-service
    Start-Service docker

    – If I tried to install Docker EE using powershell it got an SHA error and it did not install.
    – I had to use the Install-Package Docker line several times before it worked.

    I tried your script and it worked like a charm first time. Very Well done!

    One ot the benefits of EE over the Desktop Engine is that when you shutdown Windows 10 1809+ it makes a shutdown way faster.

    Reply

    • Thanks Palle!

      I noticed you used Install-Package together with download / expand archive. That’s not needed. It is just a matter of download / expand archive / register as service. Nothing more. 😉

      Yes, it is way faster, both startup and shutdown!

      Reply

  2. I ran into the same problem when installing Docker Desktop on my Windows 10 Pro laptop after that I had removed Hyper-V from it.

    Will remove Hyper-V again and try the script to install Docker-EE in coming weeks.

    Thanks for sharing this Arend-Jan!

    Reply

  3. On my Windows 10 Enterprise N Version 1809 (OS Build 17763.316) laptop, the container creation/startup of Portainer fails. This seems to be due to the fact that the Portainer image is not yet build for 1809. When I instead use the image from chocolateyfest/portainer:latest, everything works perfect.

    The question that now arises however is whether there is a difference between the container handling on Windows 10 Professional Version 1809 and Windows 10 Enterprise N 1809? Or could it be that you somehow still have Hyper-V (artifacts) installed which allows Portainer to run in hyper-v mode instead of process mode?

    Anyone attempting this setup should also be aware that many images on Docker Hub are “not yet” available as 1809 images, this includes for example SQL Server Developer Edition. You may need to build some images yourself using the nanoserver:1809 image. Fortunately that is not true for NAV/BC images as Freddy has already updated all images to enable running on 1809 OS-es. (ltsc-2019 tag) 🙂

    I hope this info helps some others running into the same issues as I did.

    Reply

    • Thanks for the heads up, Ivo.
      It worked at the moment of posting. But two days ago, the portainer image was updated to version 1.20.2. And that latest version doesn’t run anymore.
      If you pull the previous image portainer/portainer:1.20.1 it will work. Or use the image you suggest. 😉

      Opened an issue about this: https://github.com/portainer/portainer/issues/2758

      Reply

      • Thanks Arend-Jan that solved the issue. Better to stick to the official maintainers images than pulling them somewhere else as I suggested.

        Reply

  4. Pingback: Business Central Docker on Windows 10 - Gunnar's Blog - Dynamics 365 Business Central/NAV User Group - Dynamics User Group

  5. Hi,

    I tried your way to get Portainer running in Windows 10 (1809) and oit worked 🙂
    But now I am only allowed to run “Windows Images” and “Linux Images” are nt any longer allowed to run….so bad 🙁

    Or is there a way to get Linux-Images runable in this environment?

    Thanks
    Chrostoph

    Reply

    • That will not work. Linux images can’t run in process isolation on a Windows machine, you need Hyper-V isolation for that. So your only option is to install Hyper-V and Docker Desktop. The setup I described is for Windows containers only.

      Reply

  6. The docker engine installed successfully but I am missing the whale icon from the system tray. Can we enable that for docker engine version

    Reply

    • No, that is not possible. Docker engine runs as a service, it does not include a desktop icon. If you want to have the whale icon, then you should install Docker Desktop.

      Reply

  8. But why to deal with Docker EE in the first place?

    You can just use Docker CE with Hyper-V disabled – no problem at all – and you don’t even need Docker Desktop, just binaries: docker and dockerd. Link: https://master.dockerproject.org/windows/x86_64/docker.zip

    First step is to create create config file (like daemon.json) and add “exec-opts”: [“isolation=process”] and pass it to dockerd with –config-file flag or just use –isolation-process flag with docker run, like “docker run –isolation=process -itd mcr.microsoft.com/windows/nanoserver:1809 cmd”. It works, just works.

    Of course you must at first “Start-Process dockerd (…) -Verb RunAs” or run it as a service after ‘dockerd –register-service’, Start-Service docker.

    Anyway, even if you have installed Docker Desktop, which as we know forces us to enable Hyper-V, we can just disable virutalization support in Bios (like Intel Virtual Technology) and Hyper-V Windows Features, and we still be able to work with Docker service and run Windows Containers in process isolation mode, passing the correct flag. If we try to run a container with isolation=hyperv, we will receive an error: “The virtual machine could not be started because a required feature is not installed”.

    Funny observation: if virtualization is enabled in Bios, but Hyper-V Windows Features disabled, we can still run Windows Containers in hyperv isolation mode. Because Windows Containers doesn’t need Hyper-V VM! If you run the container in isolation mode, Hyper-V manager returns nothing. As far as I know the Windows Features are only needed for Linux Containers, as they need MobyLinuxVM created in Hyper-V.

    Reply

    • Remember: just bypass the GUI, like disable/remove ‘Docker for Windows.exe’ from Windows startup. Because Desktop can have annoying notifications, I work only in command line / PowerShell.

      Reply

      • I guess I’m doing the same, just download a zip file with the binaries. Someone told me the engine of CE and EE is basically the same, but I can’t tell that from the binaries. Anyway, it doesn’t really matter which one you download, right?

        So, if I get you right, you suggest to:
        * Install Docker Desktop
        * Disable Docker Desktop to run at Windows login –> this basically disables Docker
        * Register dockerd as a service –> no need for Docker Desktop at all

        I think that might work as well.

        Just one comment: don’t know if it is still the case, but if I remember correctly, Docker CE has a different pipe endpoint. I think it is pipe/docker_engine_windows instead of pipe/docker_engine (as it is on Windows Server). In my experience, I couldn’t get portainer to work with the pipe/docker_engine_windows endpoint. I had to expose port 2375 for that. But the pipe/docker_engine endpoint works fine with portainer.

        And because the DockerMsftProvider is supposed to support both Windows Server and Windows 10, I assumed it would be a good idea to fix that or to come up with an alternative to achieve the same.

        Reply

        • I have little experience with EE. If you have Docker Desktop installed, it has already Docker Engine service registered.

          Disable:
          * Docker Desktop at startup
          * Docker Desktop Service (com.docker.service)

          Leave:
          * Docker Engine service (docker)

          As for pipe name, In my case it’s docker_engine. I have Docker Engine – Community ver. 18.09.2.

          Reply

  10. Hi Aj,
    I did your steps to change also from Hyper-V Image and docker to docker engine EE direct on my laptop.
    After that I recognised a heavy cpu load on my system. Task Manager Shows my that there are allways running a lot of powershell.exe. Then I stop the Service docker engine and the heavy cpu load is gone and no powershell.exes are running.

    Do you have the same on your Computer or do you now why there are a lot of powershell.exes running, even I don’t do anything on the Computer. Just startet it.

    Reply

    • Yes, I have the same experience. It doesn’t really harm, I guess the processes you see are actually running inside the containers.
      The real downside is power consumption. Docker seems to be very hungry, my battery life is now at 50% of the normal duration.

      Reply

  11. Hi,

    Thanks for this. I’m trying to use a docker container with high memory requirement, and I understand using HyperV limits the memory use to 1GB. I’m hoping that running an alternative version on windows will allow me to add extra memory when I run the application.

    I uninstalled Docker for Desktop and have followed the option 1 (manual install) and it seems to have worked. However, when it comes to running a container I receive an error:

    “`Status: Downloaded newer image for hello-world:nanoserver
    C:\Program Files\docker\docker.exe: Error response from daemon: CreateComputeSystem 4ef51f1378e05c2970a10e7dd7d468d2f5c5396a92d3c3fdce586fa4e8cf8e4c: No hypervisor is present on this system.“`

    I didn’t think that I need a hypervisor for this system to work? Any ideas where I’m going wrong?

    Reply

    • Please try to run it in ‘process’ isolation mode, e.g. docker run -isolation=process -it –rm mcr.microsoft.com/windows/nanoserver:1809

      Reply

      • Thanks, I tried:

        `docker run –isolation process -it –rm mcr.microsoft.com/windows/nanoserver:1809`

        and initially got:

        `docker: Error response from daemon: Windows client operating systems earlier than version 1809 can only run Hyper-V containers.`

        After upgrading to version 1809

        I tried to run my own image

        “`
        docker run –isolation process -it –rm myimage:0

        docker: Error response from daemon: CreateComputeSystem fc9d7a45bf77de19bb29b5d77681e73a668b2d73239eafbde2c8a0f9c41ce154: The container operating system does not match the host operating system.
        “`

        I tried to rebuild `myimage:0`, but it seemed to just make use of the existing image (built in a second), and the error message when running it was the same.

        Any ideas on what to try next is there a way of building with `–isolation process`, i.e. building without using Hyper-V?

        Reply

        • Host OS version must be matched with the container OS version, so you should use 1809 tag in FROM part, e.g. FROM mcr.microsoft.com/windows/nanoserver:1809.

          If you just rebuild your old Dockerfile, nothing will happen, as the image is composed of cached layers.

          Reply

  12. Hi,

    Thanks a lot for this, I have followed your instructions and used it successfully for few weeks now, with zero issues!

    Previously had to delete and recreate containers every few days, now it “Just works!”(tm)

    Cheers
    Jurica

    Reply

    • Naïve question:
      If Hyper-V is not really needed for Docker Desktop for Windows, can we expect that in the (hopefully not-too-distant) future Docker can be installed not only on Windows 10 pro but also on Windows 10 home, without any special scripts?

      Reply

      • Not so sure about that. Docker client requires Hyper-V anyway, to support Linux containers. It appears most are using that, so there is little interest in changing the behavior of the Docker client.

        Reply

  14. Hello,
    I have tried option one and when I ran the script it ends with following error:

    Start-Service : Failed to start service ‘Docker Engine (docker)’.
    At C:\__TiETO\__1__PROJECTs\Playground\docker_ee.ps1:42 char:5
    + Start-Service docker
    + ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service], ServiceCommandException
    + FullyQualifiedErrorId : StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand

    Do you know, what the problem could be?

    Honza

    Reply

    • It could be the version of Windows. Are you using Windows 1809?
      I’m afraid I don’t have any suggestion, the error message is not really telling much.

      Reply

  15. Hi, I tried your Option 1. I downloaded Docker EE with

    Invoke-WebRequest -UseBasicParsing -OutFile docker-18.09.6.zip https://download.docker.com/components/engine/windows-server/18.09/docker-18.09.6.zip

    Then I ran your script, which I think it finished with success. I didn’t get any errors and in the end it asked me to restart the computer. I did and opened Powershell again, then tried to type ‘docker’ to see if the command was recognized and it’s not.

    Am I missing something?

    Reply

  16. Hello!

    I tried to make this work, but did not succeed. Container is created successfully, I can run cmd and powershell against container but cannot access to the database via C/SIDE, RTC and WebClient. Error is connection timeout.

    Also, during container installation i got a warning which says: “WARNING: DNS resolution not working from within the container.” I was investigating but till this moment no solution.

    Could you please advise anything?

    Many thanks in advance for any response.

    Reply

  17. My system is Windows 10 Pro, 1809 and I am running Virtualbox which is why I want to avoid Docker Desktop. But when I install EE according to the instructions, I get a BSOD within about 30 seconds of login. If I disable the daemon, no problem. I have not tried CE, yet, but if anyone has any suggestions, they would be appreciated.

    Oh, and I uninstalled and reinstalled and the behavior was identical. The error was:

    TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE

    Reply

    • I’m afraid I can’t help you. It could be your Windows installation, or maybe a later version of Docker that doesn’t support it anymore.
      I recommend you to ask your question on one of the Docker support forums.

      Reply

      • Will do. I’m always curious when I get an error that no one else has reported. The fact that it occurs during login/startup and the nature of the error suggests a memory leak, somewhere.

        Reply

  18. Great solution thanks! However there seems to be an issue with the executables in the cli-plugins folder. Running `docker info` returns this error for all the plugins:
    OpenSSL error: error:0F06D065:common libcrypto routines:FIPS_mode_set:fips mode not supported

    Anyone else noticed it and know how to fix it? Trying to run any of the executable in the cli-plugins folder will give the same error

    Reply

    • I’m afraid I don’t have a solution for you. It’s probably better to ask your question in any of the Docker forums or Github repo.

      Reply

  20. This works fine with a few errors which were easily corrected:

    1. The powershell script which invokes the zip download needs to verify windows version. Changing this ran the script
    2. When extracting the archive my virus software terminated powershell due to a false malware detection. MDP.Create.M1185. Killing the virus software allowed me to complete the script.

    I have portainer running now and it’s great.

    Thanks for the tip!

    Reply

  21. I was hoping someone could help me after running the script and portainer.
    I can’t pull any of the templates via portainer or powershell.

    It gives me:
    no matching manifest for windows/amd64 10.0.18362 in the manifest list entries.

    How do I mask that I’m Win 10 and am actually Win2016?

    Reply

  22. No problem during installation (option 2), ok while pulling images, but this error while starting machine:

    C:\Program Files\Docker\docker.exe: Error response from daemon: hcsshim::CreateComputeSystem 8182131e9944f27fcb18e95cf979091774bb5f6c1d5b35a22e3a65cace169453: Richiesta non supportata.

    Reply

  23. The message is:

    PS C:\WINDOWS\system32> docker run hello-world
    C:\Program Files\Docker\docker.exe: Error response from daemon: hcsshim::CreateComputeSystem 2e4e97fe97b1f4e0a66b784bf9a272f1e9046cabc86bbe37ba3e91850f747e11: Richiesta non supportata.
    (extra info: {“SystemType”:”Container”,”Name”:”2e4e97fe97b1f4e0a66b784bf9a272f1e9046cabc86bbe37ba3e91850f747e11″,”Owner”:”docker”,”IgnoreFlushesDuringBoot”:true,”LayerFolderPath”:”C:\\ProgramData\\docker\\windowsfilter\\2e4e97fe97b1f4e0a66b784bf9a272f1e9046cabc86bbe37ba3e91850f747e11″,”Layers”:[{“ID”:”594930f1-2b05-5309-a6ac-35c145504677″,”Path”:”C:\\ProgramData\\docker\\windowsfilter\\57ac82043a4bda1572a473be4875d69f591496e387c07c4e44b0879e498d3fd1″},{“ID”:”6ce711cb-9ec6-5b3a-9f9b-1773e076f569″,”Path”:”C:\\ProgramData\\docker\\windowsfilter\\3e6a8a140e2c64f9f262cdc40eafc1bf2a42f3329fb7747e5ff35cb2ef85173c”},{“ID”:”0f307b2a-74e4-5dc7-ba27-95194f6f6575″,”Path”:”C:\\ProgramData\\docker\\windowsfilter\\8d6db803e4d47630dc51eb5d1a0faa3ec083310935c82be04b9cb9ed72247887″}],”HostName”:”2e4e97fe97b1″,”HvPartition”:true,”EndpointList”:[“81045775-0E9E-453C-95CA-305270A47C6B”],”HvRuntime”:{“ImagePath”:”C:\\ProgramData\\docker\\windowsfilter\\8d6db803e4d47630dc51eb5d1a0faa3ec083310935c82be04b9cb9ed72247887\\UtilityVM”},”AllowUnqualifiedDNSQuery”:true}).

    Reply

    • Can’t say for sure. Maybe it helps to add the parameter –isolation=process to the docker run command.
      Then the command looks like: docker run –isolation=process hello-world

      Reply

      • ” PS C:\WINDOWS\system32> docker run –isolation=process hello-world

        Hello from Docker!
        This message shows that your installation appears to be working correctly. ”

        Wow.. Thank you!!
        so what’s happened? I’m so confused…

        Reply

        • Docker is by default installed with hyper-v isolation mode. If you don’t want to use that, then you need to switch to process isolation. Either by setting that in each docker run command or by changing the startup parameter of the dockerd service.

          Reply

          • I see, Thank you,
            Just a last question:
            Is that correct that i can execute docker containers just as windows administrator and not as ‘normal’ user?

          • Look at the script in option 1 of my post, there you’ll find a line that registers the service with isolation=process.
            Don’t forget to remove the service first.

  24. Hi,
    Docker service runs well, but i’ve following problem with portainer.
    After i run it and set a password, if i click on connect i receive thet error:

    Failure
    error during connect: This error may indicate that the docker daemon is not running.: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/_ping: open //./pipe/docker_engine: Access is denied.

    i’ve run portainer as:
    docker run -d –restart always –name portainer -h portainer -p 9000:9000 -v \\.\pipe\docker_engine:\\.\pipe\docker_engine portainer/portainer

    And i’ve tested opera and chrome as web browser.

    May someone help me?
    Thank you!

    Reply

    • That’s a known problem, I believe it happens when you run portainer in hyper-v isolation mode. You need to configure port 2375 for that scenario. See here for more information how to do that: https://www.portainer.io/2018/03/enable-remote-access-docker-windows-10/

      I’m running portainer in process isolation, and then I don’t get that error message. However, I had to create the portainer image myself based on the same Windows version I’m using. Haven’t checked recently, but the portainer images are not always based on the latest Windows version, so then you can’t run them with process isolation.

      Reply

      • Tanks for your answare,
        I run portainer in process isolation (“exec-opts”:[“isolation=process”] on json in docker/config) and even using string that you’ve posted:

        docker run -d –restart always –name portainer –isolation process -h portainer -p 9000:9000 -v //./pipe/docker_engine://./pipe/docker_engine portainer/portainer

        I have same result.

        Don’t know if that is the same problem, but iI try to share volumes (-v c:\test:c:\test) with dockers i receive “access denied”.

        Reply

        • This is the command I’m currently using (with my own image). The parameter -u ContainerAdministrator may make the difference. 😉

          docker run -d –isolation=process –restart always –name portainer -h portainer -p 9000:9000 -u ContainerAdministrator -v C:\ProgramData\Portainer:C:\Data -v \\.\pipe\docker_engine:\\.\pipe\docker_engine ajkauffmann/portainer:windows1909

          Reply

          • And so…The parameter -u ContainerAdministrator may made the difference ..
            Evrything is working, Thank you!

  25. While Running Option 2 Script on my local(Window 10 Pro) i am getting below error , can anyone help me with that.

    PS C:\WINDOWS\system32> $paths = $env:psmodulePath.Split(‘;’)
    $modulePath = Join-Path $paths[0] “DockerMsftProvider”
    if (!(Test-Path $modulePath)) {
    New-Item -Path $modulePath -ItemType Directory
    }
    $outfile = Join-Path $modulePath ‘DockerMsftProvider.psm1’
    Invoke-WebRequest -UseBasicParsing -OutFile $outfile -Uri https://raw.githubusercontent.com/ajkauffmann/MicrosoftDockerProvider/master/DockerMsftProvider.psm1

    $outfile = Join-Path $modulePath ‘DockerMsftProvider.psd1’
    Invoke-WebRequest -UseBasicParsing -OutFile $outfile https://raw.githubusercontent.com/ajkauffmann/MicrosoftDockerProvider/master/DockerMsftProvider.psd1

    Install-Package Docker -ProviderName DockerMsftProvider -Force

    New-Item : Could not find file ‘DockerMsftProvider’.
    At line:4 char:3
    + New-Item -Path $modulePath -ItemType Directory
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : WriteError: (C:\Users\Uday K…kerMsftProvider:String) [New-Item], FileNotFoundException
    + FullyQualifiedErrorId : CreateDirectoryIOError,Microsoft.PowerShell.Commands.NewItemCommand

    Invoke-WebRequest : Could not find a part of the path ‘C:\Users\Uday
    Khungala\Documents\WindowsPowerShell\Modules\DockerMsftProvider\DockerMsftProvider.psm1’.
    At line:7 char:1
    + Invoke-WebRequest -UseBasicParsing -OutFile $outfile -Uri https://raw …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Invoke-WebRequest], DirectoryNotFoundException
    + FullyQualifiedErrorId : System.IO.DirectoryNotFoundException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

    Invoke-WebRequest : Could not find a part of the path ‘C:\Users\Uday
    Khungala\Documents\WindowsPowerShell\Modules\DockerMsftProvider\DockerMsftProvider.psd1’.
    At line:10 char:1
    + Invoke-WebRequest -UseBasicParsing -OutFile $outfile https://raw.gith …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Invoke-WebRequest], DirectoryNotFoundException
    + FullyQualifiedErrorId : System.IO.DirectoryNotFoundException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

    Install-Package : Docker Engine – Enterprise is not supported on Windows 10 client. See https://aka.ms/docker-for-windows
    instead.
    At line:12 char:1
    + Install-Package Docker -ProviderName DockerMsftProvider -Force
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (Microsoft.Power….InstallPackage:InstallPackage) [Install-Package], Exceptio
    n
    + FullyQualifiedErrorId : RequiresWindowsServer,Install-Package,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPack
    age

    Reply

  26. Is it possible to have docker toolbox (for linux containers) running on the same PC (Windows 10 Pro but without Hyper V) and with your script have EE docker (for windows containers)?

    Reply

  27. Hi,
    I have install docker enterprise using your script. To install that, I ran powershell as administrator and ./yourscript.ps1
    Now, I can only access it if I run powershell as a administrator. I was wonder, how do I run it as standard windows user?
    In docker destop, I could add standard user in docker-user group. Now, there is no group. Any idea how to fix it?
    Thanks

    Reply

  29. Thanks for this article. These days things are even easier. If you want to run “real” Windows containers (process isolation containers, not hyperv containers) all you actually need is to install dockerd.exe as Windows service (you can download it here: https://master.dockerproject.com) and then you can connect to it with docker.exe. Super lightweight.

    sc create mydocker binPath= “c:\Program Files\mydocker\dockerd.exe -H npipe:////./pipe/mydocker -G Users –exec-opt isolation=process –run-service” start= delayed-auto && sc start

    docker -H npipe:////./pipe/mydocker ps

    https://poweruser.blog/docker-on-windows-10-without-hyper-v-a529897ed1cc

    Reply

  30. Indeed a huge CPU load. My laptop feels like a heater. With this unfortunately it seems not a good option for me. For sure when travelling as my battery will empty too fast, next to the fact that I always strive to have a as low as possible energy consumption.
    Turning of the docker service off does not to have any effect, it seems. containerd.exe keeps on running.

    Reply

Leave a Reply to Marton Nagy Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.