moby: CreateContainer Problem on Windows 10

Description At first I open this issue to https://github.com/docker/for-win/issues/361, but I was advised that it have to open here.

When I try to start container, I got a message ,Error response from daemon: container [Container Name] encountered an error during CreateContainer: failure in a Windows system call: The handle is invalid. (0x6).

Steps to reproduce the issue: I have no idea to reproduce. It seems environments error…?

Describe the results you received:

I installed docker as shown on the Microsoft homepage(https://docs.microsoft.com/ko-kr/virtualization/windowscontainers/quick_start/quick_start_windows_10).

But there is no docker-1.13.0-dev.zip, so I just replace it to docker-1.14.0-dev.zip.

I just try to run container.

PS C:\WINDOWS\system32> docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9f41f09e9678 microsoft/nanoserver “cmd” 2 hours ago Created quizzical_goodall PS C:\WINDOWS\system32> docker run -it microsoft/nanoserver cmd c:\program files\docker\docker.exe: Error response from daemon: container 73bc6ac7b17b8f5bf6ff72d8c845606d858a52badcc0a6 6d81713ff0a7113263 encountered an error during CreateContainer: failure in a Windows system call: The handle is invalid. (0x6). PS C:\WINDOWS\system32> docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 73bc6ac7b17b microsoft/nanoserver “cmd” 7 seconds ago Created adoring_ritchie 9f41f09e9678 microsoft/nanoserver “cmd” 2 hours ago Created quizzical_goodall PS C:\WINDOWS\system32>

And docker events.

PS C:\WINDOWS\system32> docker events 2016-12-29T02:50:40.758619200+09:00 container create 73bc6ac7b17b8f5bf6ff72d8c845606d858a52badcc0a66d81713ff0a7113263 (i mage=microsoft/nanoserver, name=adoring_ritchie) 2016-12-29T02:50:40.759617800+09:00 container attach 73bc6ac7b17b8f5bf6ff72d8c845606d858a52badcc0a66d81713ff0a7113263 (i mage=microsoft/nanoserver, name=adoring_ritchie) 2016-12-29T02:50:41.244616700+09:00 network connect e4eaa39f1fbe8043361ff93ea0be451f91728b039eb2b92dd0c8a7be3394937d (co ntainer=73bc6ac7b17b8f5bf6ff72d8c845606d858a52badcc0a66d81713ff0a7113263, name=nat, type=nat) 2016-12-29T02:50:42.575627800+09:00 network disconnect e4eaa39f1fbe8043361ff93ea0be451f91728b039eb2b92dd0c8a7be3394937d (container=73bc6ac7b17b8f5bf6ff72d8c845606d858a52badcc0a66d81713ff0a7113263, name=nat, type=nat) [NO MORE]

What can I do to solve this problem? Any suggestions?

Describe the results you expected: Just running container and attach container’s cmd shell.

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

PS C:\WINDOWS\system32> docker version
Client:
 Version:      1.14.0-dev
 API version:  1.26
 Go version:   go1.7.4
 Git commit:   9fab262
 Built:        Wed Dec 28 13:54:30 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.14.0-dev
 API version:  1.26 (minimum version 1.24)
 Go version:   go1.7.4
 Git commit:   9fab262
 Built:        Wed Dec 28 13:54:30 2016
 OS/Arch:      windows/amd64
 Experimental: false
PS C:\WINDOWS\system32>

Output of docker info:

PS C:\WINDOWS\system32> docker info
Containers: 2
 Running: 0
 Paused: 0
 Stopped: 2
Images: 1
Server Version: 1.14.0-dev
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: l2bridge l2tunnel nat null overlay transparent
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 14393 (14393.576.amd64fre.rs1_release_inmarket.161208-2252)
Operating System: Windows 10 Pro
OSType: windows
Architecture: x86_64
CPUs: 4
Total Memory: 3.913 GiB
Name: DESKTOP-GAMESHN
ID: RMXO:BH2E:HT6D:YNNK:QJ5Y:GDL7:G7HK:5HDH:UMAX:E4HS:TMKI:ZO5C
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
PS C:\WINDOWS\system32>

Additional environment details (AWS, VirtualBox, physical, etc.):

CPU: i5-2430M RAM: 4.00GB Model Name: Lenovo Thinkpad E420 OS: Windows 10 Pro (14393.576)

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 15 (8 by maintainers)

Most upvoted comments

Let’s try and rule some things out.  First one being networking. Try docker run --rm --net=none microsoft/nanoserver cmd /s /c echo hello.

If that works, and fails when you don’t include the --net=none, can you stop the daemon net stop docker and run it manually from an elevated command prompt with debugging enabled dockerd -D so we can get the debug logs out easily to give more clues as to what might be going on.

If including --net=none still fails, we’ll need some event logs out of the system.