docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.86k stars 292 forks source link

docker client must be run elevated - problem is not resolved! #12977

Open LexaGV opened 2 years ago

LexaGV commented 2 years ago

I have Win Server 2022 Datacenter. In features I check [x]Container (but Hyper-V is NOT checked - no need). Then I installed docker as official docs say:

Install-Module -Name DockerMsftProvider -Repository PSGallery -Force
Install-Package -Name docker -ProviderName DockerMsftProvider

Everything is installed correctly, what I checked with:

Get-Package -Name Docker -ProviderName DockerMsftProvider

...and getting this:

Name                           Version          Source                           ProviderName
docker                         20.10.9          DockerDefault                    DockerMsftProvider

But simple request for version produces this:

PS C:\Users\Administrator> docker version Client: Mirantis Container Runtime Version: 20.10.9 API version: 1.41 Go version: go1.16.12m2 Git commit: 591094d Built: 12/21/2021 21:34:30 OS/Arch: windows/amd64 Context: default Experimental: true 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/version": open //./pipe/docker_engine: The system cannot find the file specified.

As you see even simplistic setup has issue and it is NOT resolvable by DockerCli.exe -SwitchDaemon - first of all for that you need to install additional soft "Docker Desktop" (500MB program) - hell knows why I need it at all. But even after installation problem still persist. I'm disappointed how unprofessional Docker setup is made - newbies like me cannot dig in all those rakes! It could be nice somebody TEST everything from scratch before publishing any programs. And since this problem (elevated client) has mass appearance, separate page is needed to explain WHAT EXACTLY is happen and how to fix it. For me not "client", not its "elevation" makes no sense (because I even don't know WHO you name 'client') and all commands above was made IN ADMINISTRATOR SHELL - obviously all privileges was given!

Please fix setup, it's impossible to use Docker with so childish issues.

docker-robott commented 1 year ago

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

LexaGV commented 1 year ago

/lifecycle frozen