moby: Windows container: Cannot start with error "Error response from daemon: container ... encountered an error during CreateContainer: failure in a Windows system call: The system cannot find the path specified. (0x3)"

Description When I trying to start container from any image, i am receiving the error: Error response from daemon: container … encountered an error durin

Error response from daemon: container … encountered an error during CreateContainer: failure in a Windows system call: The system cannot find the path specified. (0x3)"

Several notes:

  • I was able to build and run containers on my pc, it just happened after one of the restarts
  • I did try restart the host pc, restart docker client and service, did try docker’s option “reset to default factory settings”, re-install docker, manually removing “windowsfilter” folder
  • I did try it with microsoft/aspnet:4.6.2 image (worked for me before) and microsoft/nanosererver image
  • After re-install, I am receiving similar error when trying to switch to linux containers as well (think this is related, but not sure, and it is not the main issue) with error:

The system failed to create ‘C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\MobyLinuxVM.vhdx’. at New-MobyLinuxVM, <No file>: line 218 at <ScriptBlock>, <No file>: line 375 at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Steps to reproduce the issue:

  1. Cannot describe how did I get to this point, but for now I cannot run / start any container
  2. I was able to create container by docker create --name t1 microsoft/nanoserver, but not to start it
  3. Also, Docker tray icon -> switch to linux containers failed

Host image

Diagnostic Id 59D769DD-8A58-432A-8165-4FDE4665FF05/2017-03-02_07-19-32

Docker version: Client: Version: 1.13.1 API version: 1.26 Go version: go1.7.5 Git commit: 092cba3 Built: Wed Feb 8 08:47:51 2017 OS/Arch: windows/amd64

Server: Version: 1.13.1 API version: 1.26 (minimum version 1.24) Go version: go1.7.5 Git commit: 092cba3 Built: Wed Feb 8 08:47:51 2017 OS/Arch: windows/amd64 Experimental: true

Output of docker info: Containers: 5 Running: 0 Paused: 0 Stopped: 5 Images: 1 Server Version: 1.13.1 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.447.amd64fre.rs1_release_inmarket.161102-0100) Operating System: Windows 10 Enterprise OSType: windows Architecture: x86_64 CPUs: 4 Total Memory: 15.7 GiB Name: GLB-DV-74 ID: 5DAW:KYO5:7PP4:XX65:AQYW:DO5S:PBQA:EHUP:Y6IJ:GH22:KWBL:5GX5 Docker Root Dir: C:\ProgramData\Docker Debug Mode (client): false Debug Mode (server): true File Descriptors: -1 Goroutines: 17 System Time: 2017-03-01T21:26:21.1493266+02:00 EventsListeners: 0 Registry: https://index.docker.io/v1/ Experimental: true Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

log.txt Uploading DebugInfo-2017-03-02_07-13-39.txt… Uploading log.1.txt… Uploading log.0.txt… Uploading install-log.txt…

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Comments: 24 (6 by maintainers)

Most upvoted comments

Hi everyone!

I have another problem that appeared after I restarted HNS service. Now my docker service refuses to start. In event log I see the following:

Error creating default network: HNS failed with error : {Object Exists} An attempt was made to create an object and the object name already existed

The problem seems to be in “nat” VM switch. Docker tries to re-create it but it already exists: https://i.imgur.com/jWNfBz2.jpg