Windows 11 Get http://%2F%2F.%2Fpipe%2FdockerShellPlugin-backend/exit-code : open //./pipe/dockerShellPlugin-backend: The system cannot find the file specified

Docker Desktop
,
1

I keep getting this error when trying to run an image in Docker Desktop, “Get http://%2F%2F.%2Fpipe%2FdockerShellPlugin-backend/exit-code : open //./pipe/dockerShellPlugin-backend: The system cannot find the file specified”. This issue appears to have popped up quite often over the pass several years. I have tried the suggestions in several different posts including the one here from October. I have been at this for over 3 hrs. Below are my version settings and both the Windows Subsystems for Linux and Virtual Machine Platform are enabled. Has anyone else run into this issue this year?

Windows 11
WSL version: 2.6.3.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.71
MSRDC version: 1.2.6353
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26200.7840

2

Are you sure this was the exact issue that happened often? Not just similar issues with pipes? If you are sure, can you link one? I could not find it. For some reason, not even the forum search returned your topic when searching for “dockerShellPlugin”.

I’m not even sure what this pipe is for. Based on the name I would guess that it is responsible for handling command line plugins or it is related to the Terminal feature available in Docker Desktop.

  • What command do you run to run the container?
  • Where do you run that command, in what terminal or shell? PowerShell, CMD, WSL2 distribution shell?
  • What is your Docker Desktop version?

When you share commands, logs or terminal outputs, please, use Code blocks in MarkDown or click on the </> button to start a code block to make it readable and avoid letting the forum interpreting special characters and change the visible output. Mor einfo here: https://forums.docker.com/t/how-to-format-your-forum-posts/127295#p-202628-dockerfiles-compose-files-logs-and-code-4.

3

Thanks for your response. It turns out I missed a very important System Requirement which I need at least Windows Pro to use Docker Desktop. I currently have Home Edition.

4

Docker Desktop will work with Windows Home as well. It will be restricted to the WSL2 backend, which is the recommended backend anyway.

WSL2 uses a lightweight subset of Hyper-V component, but not a full Hyper-V installation.
The Hyper-V backend requires a full Hyper-V installation, which is available starting with Windows Pro.

5

But doesn’t that involve a change or something in the Bios for windows home edition too?

6

Virtualization Technology (the exact name can vary) must be enabled in the Bios, regardless of the backend Docker Desktop is using and the Windows edition.

When I bought my current laptop, it came with Windows 11 Home edition. It ran Docker Desktop without issues with WSL2 backend on it. At one point I replaced the Home Edition license with an Enterprise license, and it continues to run without issues.

As long as WSL2 is working, Docker Desktop will work too. Though, there are various reasons why WSL2 might be broken on a Windows installation, but sadly there is no universal solution that fixes a broken WSL2 installation, because the reason it’s broken is not identical on every Windows installation. Microsoft has extensive documentation about Troubleshooting Windows Subsystem for Linux.

7

Ok. Thanks so much for sharing!

8

That’s what forums are for :slight_smile:

1 Like