Docker Compose Up gives “The system cannot find the file specified.” error

I have recently installed Docker Toolbox on my Windows 10 machine.

However, whenever I run docker-compose up I get the following error message:

Note that I have C:\Python27 and C:\Python27\Scripts in both my user and system environment variables. I also tried this using Python 3, and it still doesn’t work.

15 Answers 15

You and I may or may not have the same problem. In the link posted by @Haken Lid above, the issue is with the PATH environment variable not having the correct version of Python.

BUT, for me, the issue was that I had not set all of my environment variables, by running

before I ran the docker-compose .

I just forgot to start «Docker for Windows» which resulted in that error.

Run docker-compose with the Docker Quickstart Terminal. It will solve your error.

The Docker Quickstart Terminal is mostly a regular shell but allows to create a default machine. It can be used to connect to other machines as well:

eval $(docker-machine env )

Make sure Docker for Windows is up and running in the system tray. That was my problem.

I had this problem with a fresh install of Docker on Windows 10. My issue was that I hadn’t actually run Docker first; I just installed the .msi and ran «docker-compose» from the command line.

Once I ran Docker, (and followed a few more post-installation steps, to include logging out of and restarting my computer) I was able to run docker-compose without issue.

You can set properties by typing the following commands:

I spent close to an hour fixing this issue on my Windows machine.

1. Install Python (version 3.6.1 worked fine for me), selecting the option «add to PATH».
2. Install Docker.
3. Reboot your machine.
4. On your notification bar you’ll see an icon for Docker. Right-click it and select Settings. . Go to Shared Drives and select C: drive. You will be prompted for credentials. [*]
5. Run docker build .

Run docker-compose up .

[*]: If you don’t do this step you might see this error when on step 6: ERROR: for website Cannot create container for service website: C: drive is not shared. Please share it in Docker for Windows Settings . If after entering your credentials the C: drive isn’t checked, create a new user for your machine that has full access to the folder where you will run docker-compose up .

Can’t use Docker on Windows. open //./pipe/docker_engine: The system cannot find the file specified #5919

Comments

kamalpreetsingh24 commented Mar 3, 2020

I am using Docker Desktop 2.2.0.3 (42716) stable release in Windows 8.1 VM.
Currently, using Linux Containers and this is what I get If I run ‘Docker Version’ in Powershell.

PS C:\WINDOWS\system32> docker version
Client: Docker Engine — Community
Version: 19.03.5
API version: 1.40
Go version: go1.12.12
Git commit: 633a0ea
Built: Wed Nov 13 07:22:37 2019
OS/Arch: windows/amd64
Experimental: false
Error response from daemon: open \.\pipe\docker_engine_linux: The system cannot find the file specified.

However, If I restart Docker Desktop then it works fine but only for some time (say 10 to 15 minutes),
PS C:\WINDOWS\system32> docker version
Client: Docker Engine — Community
Version: 19.03.5
API version: 1.40
Go version: go1.12.12
Git commit: 633a0ea
Built: Wed Nov 13 07:22:37 2019
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine — Community
Engine:
Version: 19.03.5
API version: 1.40 (minimum version 1.12)
Go version: go1.12.12
Git commit: 633a0ea
Built: Wed Nov 13 07:29:19 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683

«docker run hello-world» also confirms everything is looking good
«This message shows that your installation appears to be working correctly.»

I am trying to build a Docker Image from the DockerFile and the base image which I am using is
alpine.

I expect about 20 minutes of time to build the Docker image but because of Docker Desktop stopping frequently, the image build process halts.

Is there any workaround to fix this issue?

The text was updated successfully, but these errors were encountered:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.35/info: 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. #1825

Comments

Venkateshkuntla commented Mar 13, 2018

Expected behavior

Actual behavior

Information

• Diagnostic ID from «Diagnose & Feedback» in the menu.
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)

Steps to reproduce the behavior

The text was updated successfully, but these errors were encountered:

heidricha commented Mar 13, 2018

same for me. service looks like running, but no client can connect. user- or elevated level of command line.

G508031@RMM-P7000032FW MINGW64 /
$ net start com.docker.service
The Docker for Windows Service service is starting.
The Docker for Windows Service service was started successfully.

G508031@RMM-P7000032FW MINGW64 /
$ docker version
Client:
Version: 17.12.0-ce
API version: 1.35
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:05:22 2017
OS/Arch: windows/amd64
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.35/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.

G508031@RMM-P7000032FW MINGW64 /
$ net start com.docker.service
The requested service has already been started.

shaneasullivan commented Mar 14, 2018

I had the same issue — I was able to resolve the issue by running power shell with Admin privs. I validated this was the same behavior for running the commands via elevated cmd prompt. It also enabled docker run hello-world command which was returning the error message . Access is denied. 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.

heidricha commented Mar 15, 2018

Solved for me. Run docker desktop app, check in notification. Setup if necessary.
Be happy.

rn commented Apr 30, 2018

Closing this issue. @Venkateshkuntla, if you still have the problem, please re-open and supply a diagnostics ID and detaisl of your setup (Docker for Windows version etc).

girishgodage commented Jul 18, 2018

I had the same issue — I was able to resolve the issue by running power shell with Admin privs.

«The System cannot find the file specified» on Windows 10 Login

I upgraded from Windows 7 to Windows 10 a few weeks back on my PC. Everything was going really good until yesterday when I tried to login to my windows account it was hanging and then read the message, «The System cannot find the file specified». I tried to login on all profiles and the problem persisted and would not let me in.

Any ideas on what could have caused this? More importantly, any ideas on resolutions?

Thanks for the support,

Thank you for contacting Microsoft Community. I understand that you are getting error » The System cannot find the file specified » while logging in to User Accounts . I will surely help you to fix this issue.

This issue could have occurred due to these reasons:

1. Conflict between third party applications.

2. Corrupt System Files.

Try the steps listed here:

Method 1:

I suggest you to boot the computer to Safe Mode and check if the issue occurs. If the issue do not occur in Safe Mode, I suggest you to set the computer in a clean boot state and check if it helps.

Step 1:
I suggest you to refer the article to boot to safe mode.

Step 2:
If the issue do not occur in Safe Mode, perform a clean boot and check. Setting the system in a clean boot state will help to identify if any third party applications or startup items are causing the issue.

How to perform a clean boot in Windows
http://support.microsoft.com/kb/929135

Warning: After clean boot troubleshooting steps, refer to the section «How to reset the computer to start as usual after troubleshooting with clean boot» in the provided link to return your computer to Normal startup mode.

Method 2:
If the issue persists, I suggest you to perform SFC (System File Checker) Scan from Safe Mode and check if it helps. SFC scan will scan for corrupt system files on the computer and replace them.

a. Click on Start button and type cmd in the search box.

b. Right-click on the “cmd” option and select “Run as Administrator”.

d. Type “sfc /scannow” without quotes and hit Enter.

Note: Do not close the Command Prompt Window until the verification is 100% complete. The scan results will be shown after this process is finished.

Hope this information helps. Reply to the post with an updated status of the issue so that we can assist you further.

Не можете запустить докер на Windows 10 Pro?

Проблема:

Когда я пытаюсь запустить Docker Desktop, я получаю эту ошибку.

Это вывод, когда я запускаю команду docker version на терминале.

Это работает без каких-либо ошибок, когда в окнах контейнеров. Но когда я изменяю это на контейнеры Linux, это происходит. Я много пытался найти решение этой проблемы. Но я не смог найти решение. Может кто-нибудь помочь мне решить эту проблему? Спасибо.

4 ответа

Вы можете проверить с консоли HyperV, чтобы убедиться, что есть виртуальная сеть с именем DockerNAT.

Значок в трее, чтобы увидеть, есть ли какой-то журнал, связанный с тем, почему vnet не может быть создан

Вот что работает для меня — откройте диспетчер Hyper-V и на панели «Действия» щелкните правой кнопкой мыши «Остановить службу» и подтвердите запрос. Затем установите рабочий стол Docker, который перезапустит ваш hyper-v и создаст DockerNat. Для проверки нажмите «Virtual Switch Manager» на панели «Actions», и вы должны увидеть его слева.

Вот что у меня сработало:

• Отключите настройку Hyper-V в Панели управления-> Программы и компоненты -> «Включить или отключить функции Windows».
• Перезагрузить компьютер
• После перезагрузки компьютера существующий экземпляр докера обнаружит, что ваш параметр Hyper-V отключен, и спросит вас, хотите ли вы, чтобы докер включил функцию Hyper-V.
• Нажмите «Да», чтобы докер включил функцию Hyper-V на вашем компьютере.
• Оттуда позволяют Docker запускать и делать свое дело

После выполнения этих шагов ошибка исчезла, и докер снова работал

Надеюсь, это решит вашу проблему. Наслаждайтесь!

Запуск команды MOFCOMP и перезагрузка исправили эту проблему для меня.

Выполнение этой команды: (Командная строка от имени администратора)