search

docker / for-win

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

An unexpected error occurred - "connect ENOENT \\.\pipe\errorReporter" #14191

Closed davidilag closed 1 month ago

davidilag commented 1 month ago

Description

Installed this docker installation file to Windows 11 that has WSL 2: https://desktop.docker.com/win/main/amd64/Docker%20Desktop%20Installer.exe?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-win-amd64&_gl=1*15pg1hk*_gcl_au*MzIyNDA0NTE4LjE3MTQyMzc5Njg.*_ga*MTc4NDM0MTEwNi4xNzE0MjM3OTY4*_ga_XJWPQMJYHQ*MTcyMDc5NDQ1NS41LjEuMTcyMDc5NTQ1MC42MC4wLjA.

Reproduce

  1. install Docker
  2. open Docker Desktop app

Expected behavior

That Docker Desktop app starts

docker version

Docker Desktop 4.29.0

docker info

connect ENOENT \\.\pipe\errorReporter

Diagnostics ID

7F5B1822-DE06-42EE-8569-A164E58F027E/20240712144537

Additional Info

https://docker-pinata-support.s3.amazonaws.com/incoming/3/7F5B1822-DE06-42EE-8569-A164E58F027E/20240712144537.zip

ahmad-alismail-xax commented 1 month ago

Same issue here:

Diagnostics ID: 3E31265E-34D8-48A7-913D-C7C649C235AD/20240715135441

Uploaded diagnostics to: https://docker-pinata-support.s3.amazonaws.com/incoming/3/3E31265E-34D8-48A7-913D-C7C649C235AD/20240715135441.zip

jpbriend commented 1 month ago

Can you add your Windows user to the Windows group named docker-users? Following https://docs.docker.com/desktop/release-notes/#for-windows-8

davidilag commented 1 month ago

@jpbriend , thanks. This gave me what I needed to proceed with installing Docker-Desktop.

I have two Windows users at my work, one normal and one admin. I am logged in with the normal Windows user where I am trying to install Docker. The normal user is not administrator on the computer, only the admin user. U added the normal Windows user to the Windows group called docker-users from the terminal as suggested @jpbriend. I also needed to start the Docker-Desktop app as admin.

The next error I got was related to what Docker CLI context was used. A quick ChatGPT search gave me this solution, run it in the terminal (CMD) as administrator:

Now Docker-Desktop is staring and the "welcome-to-dock" docker container is working (a simple web app with a welcome page). But it seems that I cannot add and run new images/containers.

I am getting this error after the other stuff when running the last command: _Server: ERROR: error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.45/info": open //./pipe/dockerengine: Access is denied. errors pretty printing info

ChatGPT suggests that the Docker Desktop Service Windows service is not running, which it was not. I started it, restarted the Docker-desktop app, but I still get this error. There are other suggestions to what the problem could be, some related to the fact that my normal Windows user is not administrator on the laptop I am installing Docker-desktop on. This seems to be the root problem.

I have now made my normal Windows user to admin using my admin user (in the terminal). Now things are behaving normally.

Form the terminal, after logging in to docker with the command docker login and downloading this repo: git clone https://github.com/docker/welcome-to-docker (Git for Windows needs to be installed), I am now able to run this command:

This adds the docker container to the list of images in the Docker-desktop app where I am able to start it and run the application.

jpbriend commented 1 month ago

I also agree it's an issue with your non-admin user not being admin. After adding your non-admin user to the docker-users group, did you restarted your Windows session? I suspect the group will be given to the user only on a new session.

davidilag commented 1 month ago

Hi @jpbriend I believe I did a Windows restart after this step - I restarted multiple times along the way. This is a typical Windows thing when settings like this are updated. However, it did not solve all the problems, but was one of the settings that needed to be made. I have added this step in my explanation above.

chelnak commented 1 month ago

👋 For some more context:

You may see the error message above when Docker Desktop cannot read the named pipe used for reporting errors. In most cases this is usually due to a group membership issues (as mentioned above).

We've made the default error dialog a bit more descriptive now, so it should give more of an indication of what needs to be done to resolve the issues.

davidilag commented 1 month ago

Hi @chelnak

After the process of finding out what the problem was and solving it, the initial error message kind of make sense. In the beginning it did not.

Prior to be able to install Docker Desktop, I had an issue with WSL 2 (Linux with Windows) on my new Windows 11 laptop. This is a general problem it seems. After some time googling that error I managed to get the WSL 2 working and a Ubuntu 22.04.3 LTS instance running. After that I got the error message that is described in this issue.

davidilag commented 1 month ago

I am closing this issue as Docker Desktop is working now. Please see my explanation on how I got it to work on my Windows laptop.