Error during connect in the default daemon configuration on windows

I’m trying to run Docker in process isolation mode on Windows Server 2019 (Docker Desktop does not work here, my VPS does not support Hyper-V).
I run this in PowerShell (all in Administrator mode)
docker run -it --isolation=process mcr.microsoft.com/windows/servercore:ltsc2019 cmd.exe /c ping 127.0.0.1 -t

Then I get error:

docker: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/create: open //./pipe/docker_engine: The system cannot find the file specified.
See ‘docker run —help’.

I ran command & 'C:\Program Files\Docker\DockerCli.exe' -SwitchDaemon, as suggested here: Docker cannot start on Windows

However, DockerCli.exe does not exist in a clean Docker install:

As suggested here I tried copying the file DockerCli.exe from my local Windows 10 Docker Desktop installation and reran, but then I get:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly ‘Docker.Core, Version=3.0.0.50646, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system cannot find the file specified.
at Docker.Cli.MainBackendCli.Run(IReadOnlyCollection`1 args)
at Docker.Cli.MainBackendCli.Main(String[] args)

Regardless, copying files from Docker Desktop does not feel like the right approach.

I then ran dockerd in PowerShell since that’s the only other executable in that folder:

Since I’m a newbie, I’m not sure if I just started a container and if so, which one, I just see start., but no idea where that comes from or how I can configure it.

UPDATE 1

Based on Peter Wishart’s suggestion I tried uninstall-Package -Name docker, but then I get

uninstall-Package : No package found for 'docker'. At line:1 char:1
+ uninstall-Package -Name docker
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Microsoft.Power...ninstallPackage:UninstallPackage) [Uninstall-Package]
   , Exception
    + FullyQualifiedErrorId : NoMatchFound,Microsoft.PowerShell.PackageManagement.Cmdlets.UninstallPackage

Here’s the full code of what I tried:

PS C:\Users\Administrator> uninstall-Package -Name docker
uninstall-Package : No package found for 'docker'.
At line:1 char:1
+ uninstall-Package -Name docker
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Microsoft.Power...ninstallPackage:UninstallPackage) [Uninstall-Package]
   , Exception
    + FullyQualifiedErrorId : NoMatchFound,Microsoft.PowerShell.PackageManagement.Cmdlets.UninstallPackage

PS C:\Users\Administrator> docker

Usage:  docker [OPTIONS] COMMAND

A self-sufficient runtime for containers

Options:
      --config string      Location of client config files (default
                           "C:\\Users\\Administrator\\.docker")
  -c, --context string     Name of the context to use to connect to the
                           daemon (overrides DOCKER_HOST env var and
                           default context set with "docker context use")
  -D, --debug              Enable debug mode
  -H, --host list          Daemon socket(s) to connect to
  -l, --log-level string   Set the logging level
                           ("debug"|"info"|"warn"|"error"|"fatal")
                           (default "info")
      --tls                Use TLS; implied by --tlsverify
      --tlscacert string   Trust certs signed only by this CA (default
                           "C:\\Users\\Administrator\\.docker\\ca.pem")
      --tlscert string     Path to TLS certificate file (default
                           "C:\\Users\\Administrator\\.docker\\cert.pem")
      --tlskey string      Path to TLS key file (default
                           "C:\\Users\\Administrator\\.docker\\key.pem")
      --tlsverify          Use TLS and verify the remote
  -v, --version            Print version information and quit

Management Commands:
  app*        Docker Application (Docker Inc., v0.8.0)
  builder     Manage builds
  cluster*    Manage Mirantis Container Cloud clusters (Mirantis Inc., v1.9.0)
  config      Manage Docker configs
  container   Manage containers
  context     Manage contexts
  image       Manage images
  manifest    Manage Docker image manifests and manifest lists
  network     Manage networks
  node        Manage Swarm nodes
  plugin      Manage plugins
  registry*   Manage Docker registries (Docker Inc., 0.1.0)
  secret      Manage Docker secrets
  service     Manage services
  stack       Manage Docker stacks
  swarm       Manage Swarm
  system      Manage Docker
  trust       Manage trust on Docker images
  volume      Manage volumes

Commands:
  attach      Attach local standard input, output, and error streams to a running container
  build       Build an image from a Dockerfile
  commit      Create a new image from a container's changes
  cp          Copy files/folders between a container and the local filesystem
  create      Create a new container
  diff        Inspect changes to files or directories on a container's filesystem
  events      Get real time events from the server
  exec        Run a command in a running container
  export      Export a container's filesystem as a tar archive
  history     Show the history of an image
  images      List images
  import      Import the contents from a tarball to create a filesystem image
  info        Display system-wide information
  inspect     Return low-level information on Docker objects
  kill        Kill one or more running containers
  load        Load an image from a tar archive or STDIN
  login       Log in to a Docker registry
  logout      Log out from a Docker registry
  logs        Fetch the logs of a container
  pause       Pause all processes within one or more containers
  port        List port mappings or a specific mapping for the container
  ps          List containers
  pull        Pull an image or a repository from a registry
  push        Push an image or a repository to a registry
  rename      Rename a container
  restart     Restart one or more containers
  rm          Remove one or more containers
  rmi         Remove one or more images
  run         Run a command in a new container
  save        Save one or more images to a tar archive (streamed to STDOUT by default)
  search      Search the Docker Hub for images
  start       Start one or more stopped containers
  stats       Display a live stream of container(s) resource usage statistics
  stop        Stop one or more running containers
  tag         Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE
  top         Display the running processes of a container
  unpause     Unpause all processes within one or more containers
  update      Update configuration of one or more containers
  version     Show the Docker version information
  wait        Block until one or more containers stop, then print their exit codes

Run 'docker COMMAND --help' for more information on a command.

To get more help with docker, check out our guides at https://docs.docker.com/go/guides/
PS C:\Users\Administrator> Get-PackageProvider -ListAvailable

Name                     Version          DynamicOptions
----                     -------          --------------
DockerMsftProvider       1.0.0.8          Update
msi                      3.0.0.0          AdditionalArguments
msu                      3.0.0.0
NuGet                    2.8.5.208        Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag...
PowerShellGet            1.0.0.1          PackageManagementProvider, Type, Scope, AllowClobber, SkipPublisherCheck, ...
Programs                 3.0.0.0          IncludeWindowsInstaller, IncludeSystemComponent


PS C:\Users\Administrator> Get-Package -Name Docker -ProviderName DockerMsftProvider

Name                           Version          Source                           ProviderName
----                           -------          ------                           ------------
docker                         20.10.0          DockerDefault                    DockerMsftProvider


PS C:\Users\Administrator> Install-Package -Name docker -ProviderName DockerMsftProvider

The package(s) come(s) from a package source that is not marked as trusted.
Are you sure you want to install software from 'DockerDefault'?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): y
PS C:\Users\Administrator> Install-Package -Name docker -ProviderName DockerMsftProvider

The package(s) come(s) from a package source that is not marked as trusted.
Are you sure you want to install software from 'DockerDefault'?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): A
PS C:\Users\Administrator> uninstall-Package -Name docker
WARNING: Docker Service is not available.
uninstall-Package : The property 'Status' cannot be found on this object. Verify that the property exists.
At line:1 char:1
+ uninstall-Package -Name docker
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.Power...ninstallPackage:UninstallPackage) [Uninstall-Package],
   Exception
    + FullyQualifiedErrorId : PropertyNotFoundStrict,Microsoft.PowerShell.PackageManagement.Cmdlets.UninstallPackage

PS C:\Users\Administrator>

Источник

Docker is a popular platform for building, shipping, and running distributed applications, allowing developers to create and manage containers for their applications. While Docker makes it easier for developers to deploy their applications, there are times when things don’t go as smoothly as expected. One common error that can occur is the «docker: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.» This error is encountered when the Docker client is not run with sufficient permissions and cannot connect to the Docker daemon. In this article, we’ll explore several methods for resolving this issue.

Method 1: Run Docker as administrator

To fix the «Docker: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect» issue, you can try running Docker as an administrator. Here are the steps to do it:

Right-click on the Docker icon in the system tray and select «Settings».
Go to the «General» tab and check the «Run Docker as administrator» option.
Click «Apply» and then «Restart» to apply the changes.

Alternatively, you can run Docker as an administrator using the command line. Here’s how to do it:

Open the command prompt as an administrator.
Type the following command and press Enter:
```
docker --run-as-administrator
```
This will launch Docker with administrative privileges.

You can also create a shortcut to run Docker as an administrator. Here’s how to do it:

Right-click on the desktop and select «New» > «Shortcut».
In the «Type the location of the item» field, type the following command:
```
runas /user:Administrator "C:\Program Files\Docker\Docker\Docker Desktop.exe"
```
Note: Modify the command to match the location of your Docker installation.
Click «Next» and give the shortcut a name.
Click «Finish» to create the shortcut.

Now, whenever you want to run Docker as an administrator, simply double-click on the shortcut.

That’s it! By running Docker as an administrator, you should be able to connect to the Docker daemon without any issues.

Method 2: Configure Docker daemon

To fix the «docker: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect» error, you can configure the Docker daemon with elevated privileges. Here’s how to do it:

Open the Docker Desktop application and click on the Docker icon in the system tray.
Click on «Settings» and then click on «Docker Engine».
Add the following code to the JSON configuration file:

{
  "registry-mirrors": [],
  "insecure-registries": [],
  "debug": true,
  "experimental": true,
  "hosts": ["tcp://0.0.0.0:2375", "npipe://"]
}

Save the file and restart the Docker Desktop application.
Open the Command Prompt as an Administrator.
Run the following command to set the DOCKER_HOST environment variable:

set DOCKER_HOST=tcp://localhost:2375

Run the following command to test the connection:

You should now be able to run Docker commands without elevated privileges.

Method 3: Check the Docker service status

To fix the error «docker: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect», you can try checking the Docker service status. Here are the steps to do it:

Open the Command Prompt as an administrator.
Type the following command to check the status of the Docker service:

This command will display the current status of the Docker service.
If the Docker service is not running, you can start it with the following command:
Once the Docker service is running, try running the Docker client again. If you still get the same error, try restarting the Docker service with the following command:
```
sc stop docker
sc start docker
```
This will stop and start the Docker service, which may resolve the issue.

Here’s an example code snippet:

C:\WINDOWS\system32>sc query docker

SERVICE_NAME: docker
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE,PAUSABLE,ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\WINDOWS\system32>sc stop docker

SERVICE_NAME: docker
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 3  STOP_PENDING
                                (STOPPABLE,PAUSABLE,ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x1
        WAIT_HINT          : 0x7530

C:\WINDOWS\system32>sc start docker

SERVICE_NAME: docker
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 2  START_PENDING
                                (STOPPABLE,PAUSABLE,ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x7d0

C:\WINDOWS\system32>sc query docker

SERVICE_NAME: docker
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE,PAUSABLE,ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

In summary, checking the Docker service status can help you fix the error «docker: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect».

Method 4: Verify Docker installation

To fix the error «docker: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect» using «Verify Docker installation» method, follow these steps:

Open PowerShell as an administrator.
Run the following command to verify the Docker installation:
If you see the error message «Cannot connect to the Docker daemon at tcp://localhost:2375. Is the docker daemon running?», then run the following command to start the Docker daemon:
If you see the error message «docker: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect», then run the following command to add your user account to the «docker-users» group:
```
Add-LocalGroupMember -Group "docker-users" -Member $env:USERNAME
```
Restart the Docker service by running the following command:
Finally, run the following command to verify that Docker is working correctly:

This should download and run a Docker container that prints a «Hello from Docker!» message.

That’s it! You should now be able to use Docker without any issues.

Источник

Description

About two weeks ago my pipelines were working, yesterday I tried to run but got error for first pwsh task in container:

error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Get «http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/fd8ff246ac5cd257090fd89d1c0e2ba694ee3b594be50704744fdb93928b5911/json»: open //./pipe/docker_engine: The system cannot find the file specified.

Platforms affected

Azure DevOps
GitHub Actions

Runner images affected

Ubuntu 18.04
Ubuntu 20.04
Ubuntu 22.04
macOS 10.15
macOS 11
macOS 12
Windows Server 2019
Windows Server 2022

Image version and build link

20220925.1

Is it regression?

20220905.1

Expected behavior

pwsh task executed

Actual behavior

  - pwsh: |
      $tag = '1.0.0'
      Write-Host "Create a build TAG '$tag'"
      Write-Host "##vso[build.addbuildtag]$tag"
    displayName: Set build tag

Starting: Print environment versions
==============================================================================
Task         : PowerShell
Description  : Run a PowerShell script on Linux, macOS, or Windows
Version      : 2.200.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
==============================================================================
error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Get "[http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/fd8ff246ac5cd257090fd89d1c0e2ba694ee3b594be50704744fdb93928b5911/json"](http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/fd8ff246ac5cd257090fd89d1c0e2ba694ee3b594be50704744fdb93928b5911/json%22): open //./pipe/docker_engine: The system cannot find the file specified.
##[error]Exit code 1 returned from process: file name 'C:\Windows\system32\docker.EXE', arguments 'exec -i   fd8ff246ac5cd257090fd89d1c0e2ba694ee3b594be50704744fdb93928b5911 C:\__a\externals\node\bin\node.exe C:\__w\_temp\containerHandlerInvoker.js'.
Finishing: Print environment versions

Repro steps

run pipeline:

pool:
  vmImage: "windows-2019"
container: "some_windows_container"


steps:
  - pwsh: |
      $tag = '1.0.0'
      Write-Host "Create a build TAG '$tag'"
      Write-Host "##vso[build.addbuildtag]$tag"
    displayName: Set build tag

Источник

Docker is an open platform for developing, shipping and running applications, and it provides a simple and powerful developer experience, workflows, and collaboration for creating applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. With Docker, you can manage your infrastructure in the same ways you manage your applications. By taking advantage of Docker’s methodologies for shipping, testing, and deploying code quickly, you can significantly reduce the delay between writing code and running it in production. You can download and install Docker on multiple platforms.

Refer to the following guide on how to install and uninstall Docker Desktop on Windows 10 and Windows Server, how to Pull your first Nginx Container Image from Docker Hub and deploy it to your local machine, Azure DevOps and GitHub integration for Docker and Kubernetes deployment, how to create a static pod in Kubernetes, and how to install, register and start GitLab Runner on Windows.

Executing the Windows docker version command can also prompt this error. Before using Docker Desktop, you may want to see the Docker Subscription Service Agreement. Here is a link to it.

The executor error happened due to a change in the file’s executor. The GitLab-Runner server didn’t restart to apply changes. Kindly refer to some related guides: How to install Git on macOS, clone a repository, and install software from GitHub on Windows. Panic: If you failed to register the GitLab-runner, you may be having network issues.

Running with gitlab-runner 14.3.1 (xxxxxx)
  on Windows runner with docker-windows executor xxxxxxxxx
Preparing the "docker" executor
00:07
ERROR: Failed to remove network for build
ERROR: Preparation failed: error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Get http://xxxxx/info: open //./pipe/docker_engine: The system cannot find the file specified. 
Will be retried in 3s ...

Solution: Restart the Docker service

Ensure all the prerequisites to have Docker Desktop installed and running in your environment are fulfilled. This error meant the docker daemon is unreachable. Docker daemon fails to start up on Windows or stops for some reason and especially when you try to run any commands.

To fix such types of issues restarting the service will resolve the error. This will open the Services Windows GUI. Please restart the Docker Desktop Service. This can be done by launching the services.msc from the Run dialog window or Windows Search.

Right-click on Docker Desktop and select the restart option. Please make sure the services are in the “Running” state.

Docker Platform Installation Deployment Integration Guide: Restart the Docker Service Via the command line

The Docker Desktop services can be stopped and restarted with the following commands. Regardless of the step you use, you will achieve the same result.

net stop com.docker.service
net start com.docker.service

Restart docker service using GUI

Using Docker Desktop GUI, click on the troubleshooting icon as shown below and click on Restart.

Click the hidden icon, right-click on Docker, and restart it by following the Docker Platform Installation Deployment Integration Guide steps.

After following the steps outlined in the Docker Platform Installation Deployment Integration Guide, the error was resolved by restarting the Docker Desktop and the GitLab-Runner service using any of the mentioned methods. If the steps above do not resolve your issues (errors), you may have to Switch Daemon configuration “Switch to Windows Container” in your host OS is Windows.

PS C:\Program Files\Docker\Docker> ./DockerCli.exe -SwitchDaemon

You can perform this action using the command prompt below or directly from the taskbar. To switch to Windows, right-click on the white whale as detailed in the Docker Platform Installation Deployment Integration Guide. Here are some similar errors this method can resolve as well: “Docker image OS”windows” cannot be used on this platform: No matching manifest for linux/amd64 in the manifest list entries from Microsoft Docker Registry“, and “The executor requires OSType=windows, but Docker Engine supports only OSType=linux“.

I trust you found the Docker Platform Installation Deployment Integration Guide useful. Kindly share any queries in the comments section.

Источник

Docker: Error During Connect: In The Default Daemon Configuration On Windows With Code Examples

In this session, we’ll try our hand at solving the Docker: Error During Connect: In The Default Daemon Configuration On Windows puzzle by using the computer language. The code that follows serves to illustrate this point.

$ docker-machine restart default
$ eval $(docker-machine env default)
// Apparently you need to run the eval $(docker-machine env default) every time you run the quick start terminal.

The various approaches to solving the Docker: Error During Connect: In The Default Daemon Configuration On Windows problem are summarised in the following code.

cd "C:\Program Files\Docker\Docker" ; ./DockerCli.exe -SwitchDaemon

C:\Projects> docker version
Client:
 Version:      1.13.0-dev
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   d8d3314
 Built:        Tue Nov  1 03:05:34 2016
 OS/Arch:      windows/amd64
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.25/version: open //./pipe/docker_engine: The system cannot find the file
specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.



||||||||||||| FIX  |||||||||||||
The error is related to that part:

In the default daemon configuration on Windows, the docker client must be run elevated to connect

You can do this in order to switch Docker daemon, as elevated user:

With Powershell:

Open Powershell as administrator
Launch command: & 'C:\Program Files\Docker\Docker\DockerCli.exe' -SwitchDaemon
OR, with cmd:

Open cmd as administrator
Launch command: "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemon

We investigated a wide range of use cases in order to find a solution to the Docker: Error During Connect: In The Default Daemon Configuration On Windows problem.

How do I fix this error during connect this error may indicate that the Docker daemon is not running?

We can do this in order to switch Docker daemon:

With Powershell: Open Powershell as administrator. Launch command: & ‘C:\Program Files\Docker\Docker\DockerCli.exe’ -SwitchDaemon.
OR, with cmd: Open cmd as administrator. Launch command: «C:\Program Files\Docker\Docker\DockerCli.exe» -SwitchDaemon.

How do I enable Docker daemon in Windows?

To start Docker in daemon mode, choose Application > Start «Docker Daemon». The state should transition to «Running» after a few seconds and Docker Daemon should be accessible over the remote bridge. That’s it! Next time your computer boots, Docker Daemon will start up immediately, before anyone logs on.16-Apr-2022

How do I run a Docker client elevated in Windows?

In the default daemon configuration on Windows, the docker client must be run elevated to connect.

Download docker desktop from docker hub after login to docker.
Install Docker Desktop Installer.exe using Run as administrator -> Mark windows container during installation else it will only install linux container.

C:\ProgramData\docker

How do I start Docker daemon in Windows command line?

You can also stop Docker for Windows and run just the Docker daemon dockerd.exe .Note- If you have already had running Docker containers running on your system then don’t follow these steps. You may lose the exiting containers.

Start->Run-> services.msc.
Search for service named «Docker»
Start service.

Why is Docker not working Windows 10?

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.

How do I connect to Docker daemon?

How to Connect to a Remote Docker Daemon

sudo mkdir -p /etc/systemd/system/docker.service.d.
sudo nano /etc/systemd/system/docker.service.d/options.conf.
[Service] ExecStart= ExecStart=/usr/bin/dockerd -H unix:// -H tcp://0.0.0.0:2375.
# Reload the systemd daemon.

How do I run Docker daemon on Windows Server 2019?

How to run Docker Containers on Windows Server 2019

Step 1: Enable the containers feature in Windows Server 2019. The first step is to enable the Windows Server 2019 containers feature.
Step 2: Install Docker on Windows Server 2019.
Step 3: Run Docker Container.

What is the Docker daemon?

Docker daemon is a persistent background process that manages the containers on a single host. It is a self-sufficient runtime that manages Docker objects such as images, containers, network, and storage. Docker daemon listens for REST API requests and performs a series of container operations accordingly.29-Jan-2020

How do I run Docker daemon with elevated privileges?

Go to the directory where the Docker is installed on your Windows installation drive and find a file named «Docker for Windows.exe», right click it and run it as administrator.12-Aug-2019

Источник