Hi everyone,
I install docker for windows on my office computer for testing it.
The computer is equipped with windows 10 pro / 64 bit.
After some struggle with the startup of the docker service I switch to windows container
and now the docker icon in systray show the tooltip “docker is running”.
I try the command docker version and it retunning the following output:
PS C:\WINDOWS\system32> docker version
Client:
Version: 17.09.0-ce
API version: 1.32
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:40:09 2017
OS/Arch: windows/amd64
Server:
Version: 17.09.0-ce
API version: 1.32 (minimum version 1.24)
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:50:27 2017
OS/Arch: windows/amd64
Experimental: true
PS C:\WINDOWS\system32>
So everything seems to be fine!
The next step is running the “hello-world” to ensure this.
Unfortunately something goes wrong, here the output:
PS C:\WINDOWS\system32> docker run hello-world
Unable to find image ‘hello-world:latest’ locally
latest: Pulling from library/hello-world
bce2fbc256ea: Pull complete
b0b5e40cb939: Pull complete
87377cdc7dd1: Pull complete
7d840042f15f: Pull complete
Digest: sha256:07d5f7800dfe37b8c2196c7b1c524c33808ce2e0f74e7aa00e603295ca9a0972
Status: Downloaded newer image for hello-world:latest
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: container
b50b38cb82f2855ab3a954c70303d4820f6553309adb433b5004598eaada4614
encountered an error during CreateContainer: failure in a Windows system call: The extended attributes are inconsistent.
(0xff) extra info: {“SystemType”:“Container”,“Name”:“b50b38cb82f2855ab3a954c70303d4820f6553309adb433b5004598eaada4614”,“Owner”:“docker”,“IgnoreFlushesDuringBoot”:true,“LayerFolderPath”:“C:\ProgramData\Docker\windowsfilter\b50b38cb82f2855ab3a954c70303d4820f6553309adb433b5004598eaada4614”,“Layers”:[{“ID”:“4
5ca24bd-4612-57a9-83b6-df799b868285”,“Path”:“C:\ProgramData\Docker\windowsfilter\3205728ad5d5bf7454d1dca7607b7d2060fd8d349903c4a204cd427ac82b24b7”},{“ID”:“cefea608-38e2-51a7-8188-64c255e0c21b”,
“Path”:“C:\ProgramData\Docker\windowsfilter\1c63e304c18e9a63110c7b35b364e51615f4fcd32aa8a7826fb75b1d5ab3c17c”},{“ID”:“045cb882-2897-56b4-8383-d3e879431995”,“Path”:“C:\ProgramData\Docker\wind
owsfilter\bfe3d663f500472680c9c3fd65b25a64dc3b05e05881fbeb5bd695b58539e027”},{“ID”:“48fc6188-7e68-5e3d-a739-b6b3c8eaec27”,“Path”:“C:\ProgramData\Docker\windowsfilter\fb6fdccf7abfd2bd962c8e9fe2
66e6bd45f63d6d4c3909a693607ada38a653c9”}],“HostName”:“b50b38cb82f2”,“HvPartition”:true,“EndpointList”:[“2f78f154-b537-4e02-b556-0b08a5911c1d”],“HvRuntime”:{“ImagePath”:“C:\ProgramData\Docker\win
dowsfilter\bfe3d663f500472680c9c3fd65b25a64dc3b05e05881fbeb5bd695b58539e027\UtilityVM”},“AllowUnqualifiedDNSQuery”:true}.
In addiction I see in HyperV console to ensure the state of MobyLinuxVM and find it switch off.
Trying to start the vm I get an error “Unable to start MobyLinuxVM”
What mistake I’m doing?
Someone has similar error experiences?
Thanks in advance for your kind answer.
Nunzio