moby: Cannot locate Windows named pipe "docker_engine" after passing -v \\.\pipe\docker_engine:\\.\pipe\docker_engine
Description
I’m trying to mount the docker named pipe to a container in order to communicate with the docker host on the same machine. I’m using pipelist64.exe from SysInternals to inspect named pipes in the container (https://docs.microsoft.com/en-us/sysinternals/downloads/pipelist) Steps to reproduce the issue:
- Use this docker file to build the image
FROM microsoft/windowsservercore:latest
WORKDIR /app
COPY pipelist64.exe .
- Run the container with
docker run -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -i image
- at the command prompt, run
pipelist64.exe -accepteula
Describe the results you received:
PipeList v1.02 - Lists open named pipes
Copyright (C) 2005-2016 Mark Russinovich
Sysinternals - www.sysinternals.com
Pipe Name Instances Max Instances
--------- --------- -------------
InitShutdown 3 -1
lsass 5 -1
ntsvcs 3 -1
scerpc 3 -1
Winsock2\CatalogChangeListener-444-0 1 1
epmapper 3 -1
Winsock2\CatalogChangeListener-100-0 1 1
LSM_API_service 3 -1
eventlog 3 -1
Winsock2\CatalogChangeListener-4c0-0 1 1
TermSrv_API_service 3 -1
Ctx_WinStation_API_service 3 -1
wkssvc 6 -1
winreg 3 -1
cexec-141 1 1
cexec-142 1 1
cexec-143 1 1
Winsock2\CatalogChangeListener-228-0 1 1
Winsock2\CatalogChangeListener-4fc-0 1 1
SessEnvPublicRpc 3 -1
Winsock2\CatalogChangeListener-290-0 1 1
Describe the results you expected:
I expect to see docker_engine
in the list
Output of docker version
:
Client:
Version: 18.03.0-ce-rc1
API version: 1.37
Go version: go1.9.4
Git commit: c160c73
Built: Thu Feb 22 02:34:04 2018
OS/Arch: windows/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.03.0-ce-rc1
API version: 1.37 (minimum version 1.24)
Go version: go1.9.4
Git commit: c160c73
Built: Thu Feb 22 02:41:20 2018
OS/Arch: windows/amd64
Experimental: true
Output of docker info
:
Containers: 15
Running: 2
Paused: 0
Stopped: 13
Images: 11
Server Version: 18.03.0-ce-rc1
Storage Driver: windowsfilter (windows) lcow (linux)
Windows:
LCOW:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gelf json-file logentries splunk syslog
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 16299 (16299.15.amd64fre.rs3_release.170928-1534)
Operating System: Windows 10 Enterprise
OSType: windows
Architecture: x86_64
CPUs: 16
Total Memory: 31.94GiB
Name: DevStation9
ID: UUVQ:NZ2B:DUES:KFDG:ZSTT:VSS2:CM3J:G5GV:NXY2:CTHA:YTKX:YC4G
Docker Root Dir: C:\ProgramData\Docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: -1
Goroutines: 69
System Time: 2018-03-12T10:05:02.8901376-04:00
EventsListeners: 1
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Please let me know if you need more information.
Thanks,
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 22 (7 by maintainers)
This is fixed in Windows builds > 17054. Windows Server version 1803 and Windows 10 version 1803 will have the fix once they’re released.
Named Pipes are only supported on Server Core 1709/1803 and Server 2019
@ralsu091 i’ve been able to repro this when using hyper-v isolation as your
docker info
shows, and that it works properly when using process isolation