Windows named pipe error: The system cannot find the file specified. (code: 2)

[winzapbr]

run docker.sh

=====
Windows named pipe error: The system cannot find the file specified. (code: 2)

Waiting for Elasticsearch ... done
Waiting for kibana ... (forever)

I'm using Windows 10 with docker-toolbox

[Wicker25]

Hi, @winzapbr ,

Thank you for bringing this issue to my attention!
I didn't test WhatsTrapp on Windows yet but it could be a problem with the port binding.

Could you share with me the output of the command docker-compose up? Can you also check if you can access http://127.0.0.1:9200/ (Elasticsearch's entrypoint) and http://127.0.0.1:5601 (Kibana's entrypoint)?

Thank you again!

[winzapbr]

Oi, @winzapbr ,

Obrigado por trazer este assunto à minha atenção!
Eu não testei o WhatsTrapp no Windows ainda, mas pode ser um problema com a ligação de porta.

Você poderia compartilhar comigo a saída do comando docker-compose up? Você também pode verificar se consegue acessar http://127.0.0.1:9200/ (ponto de entrada do Elasticsearch) e http://127.0.0.1:5601 (ponto de entrada do Kibana)?

Obrigado de novo!

output of the command docker-compose up:
Windows named pipe error: The system cannot find the file specified. (code: 2)

Elasticsearch's entrypoint http://127.0.0.1:9200/: OK
Kibana's entrypoint http://127.0.0.1:5601 : OFF

Thank you for the urgent response.

[winzapbr]

I believe the problem is specifically in the docker and kibana!
You can produce version for windows. It will be of great generosity.

[winzapbr]

I believe the problem is specifically in the docker and kibana!
You can produce version for windows. It will be of great generosity.

screenshot https://i.imgur.com/RVCXoCz.png

[AshwinParmar]

I having same issue, Can somebody let me know, what was the issue?

Docker state is Running on Windows 10
when I am executing docker-compose up -d it will give error as follow:
Windows named pipe error: The system cannot find the file specified. (code: 2)

Docker version getting following error:

$ docker version
Client: Docker Engine - Community
Version: 18.09.0
API version: 1.39
Go version: go1.10.4
Git commit: 4d60db4
Built: Wed Nov 7 00:47:51 2018
OS/Arch: windows/amd64
Experimental: false
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/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.

[maqui7295]

Please I have the same issue

docker version

Client: Docker Engine - Community
Version: 18.09.1
API version: 1.39
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:34:26 2019
OS/Arch: windows/amd64
Experimental: false
**error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.39/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.**

[Wicker25]

Hi, folks,

I reopened the issue considered that many people are getting the same. Could you check this other conversation for me: docker/for-win#1825?

It seems to be a privilege issue with docker running in Windows.

[ABQJuan]

I too just started having this issue.

[kaynetik]

@ABQJuan @maqui7295 Just experienced the same issue. Resolved it with following simple steps:

1. Clean up local Docker env:

docker image prune
docker container prune
docker network prune

2. Dump current credentials using Docker > Settings GUI:
   

I didn't find the actual reason that was causing this issue. But I'll keep an open eye, in order to properly report this as a ticket for windows docker client.

☮️ ✌️

[zeabdelkhalek]

Same issue here

[anigithubbain]

I got the issue resolved by running the cmd with Run As Administrator.