docker / for-win Goto Github PK

Expected behavior

Expect "google.com" to resolve while connected to VPN

Actual behavior

"google.com" does not resolve while connected to VPN

Information

• Diagnostic ID: D90C5FE2-32AC-486E-AB8E-EF1EF4E0036E/2016-08-17_12-45-07
• Windows 10 Enterprise 10511 (Build 10586.545)
• Docker for Windows Beta

Steps to reproduce the behavior

1. Connect to AnyConnect VPN with split DNS enabled
2. Start a docker container (i.e., alpine) and attempt to ping google.com

Conversely, if I am NOT connected to the VPN, I can successfully resolve google.com (however, not any internal network names).

Additional Notes

It appears that the com.docker.slirp.exe proxy process is intercepting the DNS queries successfully but instead of sending them through the AnyConnect interface, it is attempting to forward the query directly to my corporate network's DNS server (probably the default on the interface), which doesn't allow external domains to be resolved.

You can see this behavior below, logs were gathered with:
gc $(gi $env:LocalAppData\Docker\* | sort LastAccessTime -Desc | select -First 1) -Wait

[12:57:52.243][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[c968] 192.168.65.2:40099 -> 192.168.65.1 c968 Query:0 na:c:r:rn 0 <qs:google.com. <A|IN>> <an:> <au:> <ad:>
[12:57:52.244][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[c968] 192.168.65.2:40099 -> 192.168.65.3 c968 Query:0 na:c:r:rn 0 <qs:google.com. <A|IN>> <an:> <au:> <ad:>
[12:57:52.244][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[cd50] 192.168.65.2:40099 -> 192.168.65.1 cd50 Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:57:52.244][ApiProxy       ][Info   ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 51560 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0  ;; QUESTION SECTION: ;google.com.        IN
 A
[12:57:52.245][ApiProxy       ][Info   ] Search for dns server...
[12:57:52.245][VpnKit         ][Error  ] com.docker.slirp.exe: Error reading /etc/resolv.conf: reading /etc/resolv.conf: Uwt.Uwt_error(Uwt.ENOENT, "uv_fs_open", "/etc/resolv.conf")
[12:57:52.247][ApiProxy       ][Info   ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 52560 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0  ;; QUESTION SECTION: ;google.com.        IN
 AAAA
[12:57:52.248][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[c968] Forwarding to 10.0.75.1 (secondary(wrapped))
[12:57:52.249][VpnKit         ][Debug  ] com.docker.slirp.exe: Socket.Datagram.input 192.168.65.2:40099-10.0.75.1:53 (DNS[c968]): creating UDP NAT rule
[12:57:52.249][ApiProxy       ][Info   ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 51560 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0  ;; QUESTION SECTION: ;google.com.        IN
 A
[12:57:52.250][VpnKit         ][Error  ] com.docker.slirp.exe: Error reading /etc/resolv.conf: reading /etc/resolv.conf: Uwt.Uwt_error(Uwt.ENOENT, "uv_fs_open", "/etc/resolv.conf")
[12:57:52.250][ApiProxy       ][Info   ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 52560 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0  ;; QUESTION SECTION: ;google.com.        IN
 AAAA
[12:57:52.250][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[c968] Forwarding to 10.0.75.1 (primary(sole))
[12:57:52.252][VpnKit         ][Error  ] com.docker.slirp.exe: Error reading /etc/resolv.conf: reading /etc/resolv.conf: Uwt.Uwt_error(Uwt.ENOENT, "uv_fs_open", "/etc/resolv.conf")
[12:57:52.252][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[cd50] Forwarding to 10.0.75.1 (primary(sole))
[12:57:52.253][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[cd50] 192.168.65.2:40099 -> 192.168.65.3 cd50 Query:0 na:c:r:rn 0 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>
[12:57:52.253][VpnKit         ][Error  ] com.docker.slirp.exe: Error reading /etc/resolv.conf: reading /etc/resolv.conf: Uwt.Uwt_error(Uwt.ENOENT, "uv_fs_open", "/etc/resolv.conf")
[12:57:52.254][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[cd50] Forwarding to 10.0.75.1 (secondary(wrapped))
[12:57:54.233][ApiProxy       ][Info   ] Server:  hqdc1.hq.practicefusion.com
[12:57:54.234][ApiProxy       ][Info   ] Address:  10.17.14.11
[12:57:54.234][ApiProxy       ][Info   ]
[12:57:54.235][ApiProxy       ][Info   ]
[12:57:54.236][ApiProxy       ][Info   ] Found dns server 10.17.14.11
[12:57:54.237][ApiProxy       ][Info   ] Forward DNS query on udp to 10.17.14.11:53
[12:57:54.237][ApiProxy       ][Info   ] Forward DNS query on udp to 10.17.14.11:53
[12:57:54.238][ApiProxy       ][Info   ] Forward DNS query on udp to 10.17.14.11:53
[12:57:54.239][ApiProxy       ][Info   ] Forward DNS query on udp to 10.17.14.11:53
[12:57:54.240][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[cd50] 192.168.65.2:40099 <- secondary(wrapped) (c968 Response:0 na:c:r:rn 3 <qs:google.com. <A|IN>> <an:> <au:> <ad:>)
[12:57:54.240][ApiProxy       ][Info   ] Got response ;; opcode: QUERY, status: NXDOMAIN, id: 51560 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0  ;; QUESTION SECTION: ;google.com.        IN
 A
[12:57:54.241][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[cd50] 192.168.65.2:40099 <- secondary(wrapped) (cd50 Response:0 na:c:r:rn 3 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>)
[12:57:54.242][ApiProxy       ][Info   ] Got response ;; opcode: QUERY, status: NXDOMAIN, id: 52560 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0  ;; QUESTION SECTION: ;google.com.        IN
 AAAA
[12:57:54.242][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[cd50] 192.168.65.2:40099 <- secondary(wrapped) (cd50 Response:0 na:c:r:rn 3 <qs:google.com. <AAAA|IN>> <an:> <au:> <ad:>)
[12:57:54.246][ApiProxy       ][Info   ] Got response ;; opcode: QUERY, status: NXDOMAIN, id: 52560 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0  ;; QUESTION SECTION: ;google.com.        IN
 AAAA
[12:57:54.247][ApiProxy       ][Info   ] Got response ;; opcode: QUERY, status: NXDOMAIN, id: 51560 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0  ;; QUESTION SECTION: ;google.com.        IN
 A
[12:57:54.247][VpnKit         ][Info   ] ICMP Destination Unreachable: Destination port unreachable
[12:57:54.246][VpnKit         ][Debug  ] com.docker.slirp.exe: DNS[cd50] 192.168.65.2:40099 <- secondary(wrapped) (c968 Response:0 na:c:r:rn 3 <qs:google.com. <A|IN>> <an:> <au:> <ad:>)
[12:57:54.248][VpnKit         ][Info   ] ICMP Destination Unreachable: Destination port unreachable
[12:57:57.250][VpnKit         ][Debug  ] com.docker.slirp.exe: ARP responding to: who-has 192.168.65.1?
[12:57:57.251][VpnKit         ][Debug  ] com.docker.slirp.exe: ARP responding to: who-has 192.168.65.3?

Expected behavior

When trying to login to an internal docker registry with:
docker login registry.isc.ejpd.admin.ch
Expected successful login acknowledged with the message
"Login Succeeded"
The exact same command run successfully from a Linux host.

Actual behavior

Login fails with:
"Error response from daemon: Get https://registry.isc.ejpd.admin.ch:5000/v1/users/: x509: certificate signed by unknown authority"

Information

Diagnostic ID: 6BB9DE18-179E-43B2-8240-FA7CC6431D73/2016-08-12_10-21-58

The registry uses a self-signed Certificate (See attached file registry.crt.txt, remove txt-extension)

The CA-Certificate is added to the following locations on the Windows-filesystem:
C:\ProgramData\Docker\certs.d\registry.isc.ejpd.admin.ch
C:\ProgramData\Docker\certs.d\registry.isc.ejpd.admin.ch5000

Restarted Docker & even rebooted the Machine

Windows Version: Windows 10 Pro Version 1607 (OS Build 14393.10)
Docker for Windows: 1.12.0-stable (Build 5968)

The login also fails, if I connect to the MobyLinuxVM and execute the login-command there. I was not able to find the CA-Cert on the MobyLinuxVM. Looks like the certificates are not propagated from the Windows-Filesystem into the MobyLinuxVM

Steps to reproduce the behavior

1. Start an internal docker registry with a self-signed certificate
2. Add the registry-certificate to C:\ProgrammData\Docker\certs.d<>
3. Try to login to the registry with: docker login <>

Expected behavior

a sqlite database file can be place is a folder mounted from the host and used normally

Actual behavior

any operation on such database results in a "database is locked" error
database files placed in non-mounted folder work as expected

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  90E72802-EF07-4D06-8B68-EC91E23CDBBE/2016-07-29_20-36-27
• host distribution and version (Windows version, build number, etc)

> [System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      10586  0

Steps to reproduce the behavior

1. docker run --rm -it -v /c/Users/alebi/Desktop/db/data:/data --name sqlite sqlite /data/data.db
2. .database

seq  name             file
---  ---------------  ----------------
0    main             /data/data.db

1. CREATE TABLE IF NOT EXISTS foo(bar int);
Error: database is locked

Additional info

These are the mounting options

> docker run --rm -v /c/Users/alebi/Desktop/db/data:/data alpine cat /proc/self/mountinfo | Select-String -pattern "/data"

122 102 0:40 /Users/alebi/Desktop/db/data /data rw,relatime - cifs //10.0.75.1/C
rw,vers=1.0,cache=strict,username=alebi,domain=ANTARES,uid=0,noforceuid,gid=0,noforcegid,addr=10.0.75.1,file_mode=0755,dir_mode=0755,iocharset=utf8,nounix,serverino,mapposix,noperm,rsize=61440,wsize=65536,actimeo=1

This seems to be a "common" CIFS issue related to the byte-range blocking that behaves unexpectedly with sqlite locks. It's usually resolved by using the nobrl flag in the mounting options.

The MobyLinux.ps1 script (C:\Program Files\Docker\Docker\resources) used to contain the mount flags, were I could add the nobrl option when needed, as of the latest version (1.12.0-beta21) the mount flags were removed so there's no workaround (yet).

Expected behavior

Able to change the virtualization back end used by Docker for Windows to accomodate scenarios where the user already has a virtualization product installed.

Actual behavior

Docker for Windows requires Hyper-V which doesn't co-exist with other virtualization platforms for windows (e.g. Virtualbox, VMWare Workstation)

Information

It would be really nice if it was possible to swap out what virtualization backend is used by Docker for windows. There are likely a large number of potential users who already have a virtualization platform installed, and so can't install this, as in general virtualization platforms don't co-exist well on a given OS install.

Cute Animal Picture

Expected behavior

Folders in the user's space can be mounted in a container without additional configurations.
Folder is mounted with cifs filesystem

Actual behavior

Mounted folders turns out to be empty unless the C drive is shared
Folder is mounted with tmpfs filesystem

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  90E72802-EF07-4D06-8B68-EC91E23CDBBE/2016-07-29_20-12-28
• a reproducible case if this is a bug, Dockerfiles FTW

> Get-ChildItem .\data\ | Select-Object Name
Name
----
test.sql
> docker run --rm -v /c/Users/alebi/Desktop/db/data:/data alpine ls -la /data
total 4
drwxr-xr-x    2 root     root            40 Jul 29 17:40 .
drwxr-xr-x   25 root     root          4096 Jul 29 17:56 ..

> docker run --rm -v /c/Users/alebi/Desktop/db/data:/data alpine cat /proc/self/mountinfo | Select-String -pattern "/data"

110 90 0:16 /c/Users/alebi/Desktop/db/data /data rw,relatime - tmpfs tmpfs rw

• host distribution and version (Windows version, build number, etc)

> [System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      10586  0

Steps to reproduce the behavior

1. nothing.

Execute run hello-world in a 'docker for windows' environment.

Expected behavior

Unable to find the image locally, so downloads from dockerhub

Actual behavior

Network times out consistently

docker run hello-world
Unable to find image 'hello-world:latest' locally
Pulling repository docker.io/library/hello-world
docker: Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/hello-world/images. You may want to check your internet connection or if you are behind a proxy..
See 'docker run --help'.

Information

Looks like a proxy/dns issue, but the logs don't make much sense to me.
Docker for windows 1.12.0-stable build 5968

Steps to reproduce the behavior

1. run hello-world
2. cry

Expected behavior

Xbox One App Chats should work. Maybe Skype is also affected as they use the same network stack.

Actual behavior

When Docker is installed the Xbox App Chat (Party) is not able to connect anymore, none the less the
teredo status shows that everything is fine: type: qualified

Disabling the Hyper-V network interfaces solved the issue for me.

Information

Windows 10 Pro 1607

Expected behavior

Pulling hello-world when I am not behind proxy.

Actual behavior

> docker run hello-world
Unable to find image 'hello-world:latest' locally
Pulling repository docker.io/library/hello-world
docker: Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/hello-world/images. You may want to check your internet connection or if you are behind a proxy..
See 'docker run --help'.`

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  6412C29D-46BA-4A66-BF45-1681D9ED06C0/2016-08-04_10-35-01

• host distribution and version (Windows version, build number, etc)

  > ver
  Microsoft Windows [Version 10.0.10586]`
  

Steps to reproduce the behavior

1. Uninstall Docker for Windows 10
2. Install Docker for Windows 10
3. run docker run hello-world

Expected behavior

A php application inside a i386 container should be able to recognize directories when using calls like 'stat' and 'is_dir' on mounted volumes.

Actual behavior

'stat' and 'is_dir' return false when executing the command on a mount volume path.

Information

The following stackoverflow post explains the issue:
http://stackoverflow.com/questions/26718203/php-file-directory-stat-related-functions-do-not-work-on-mounted-cifs

I have now created a remount tool (simple console app) as a temporary solution, that unmounts, and mounts the drives again with the added mount option.
In the method "CifsOptions" (Cifs.cs), I have added stringList.Add("noserverino"); just before the return string join.
Then simply do the same thing the app does, load settings, retrieve credentials, loop the SharedDrives setting, and umount+mount the drive.

I don't think it does any harm if the option is added in the application, but I could be wrong.

Perhaps it would be nice to make this part of some sort of advanced options?

If the option can not be added, and the advanced option thing is also not possible I have to wait until Docker for windows gets a proper source release, patching the dll's just for this seems overkill to me :)

Steps to reproduce the behavior

Host system: Windows 10 Pro x64 (issue is probably only on x64 systems, not sure)

Create a docker container based on 32bit/debian
Install PHP (5.3)
Run the container and mount for example your c drive to /mnt
in the container, execute this bit of code:

C:\Users\m\src\phr\docker\local [develop ≡]> docker run -it -v C:\Users\m\src\phr\docker\local\broker-config.yml:/cryptoservice/broker-config.yml image-name bash

C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: oci runtime error: rootfs_linux.go:53: mounting "/var/lib/docker/aufs/mn t/90d24356afdeb7b9ddad4b3b6903be92063151c33bf34f3d63ede464437060c6/cryptoservice/broker-config.yml" to rootfs "/var/lib/docker/aufs/mnt/90d24356afdeb7b9ddad4 b3b6903be92063151c33bf34f3d63ede464437060c6" caused "not a directory".

Expected behavior

Similarly to how Docker behaves on Linux, the container should start.

Actual behavior

See above

Information

This happens on Win10 latest (1511?) + Docker 1.12, and with Mac as well (can't provide version for now).
I'll try to make an image with which this is reproducible.

It appears the source of https://docs.docker.com/docker-for-windows/ is not on GitHub. Could that be open sourced so we can suggest improvements?

Expected behavior

Docker should start

Actual behavior

Docker does not start

Information

Diagnostic ID: E0BC3065-6B9C-4BB1-83EF-966436C17D7A/2016-08-10_10-46-01

I'm getting this error, after starting my computer this morning.
OS: Latest Win 10 Pro Version (Version: 1607 Build: 1493.10)
Architecture: x64

The following Stacktrace is shown to me:

Failed to create VM "MobyLinuxVM": Für "min" und die folgende Argumenteanzahl kann keine Überladung gefunden werden: "2".
   bei Docker.Core.Pipe.NamedPipeClient.TrySend(String action, Object[] parameters)
   bei Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
   bei Docker.Core.Backend.BackendClient.Start(Settings settings)
   bei Docker.Actions.DoStart(Settings settings, Boolean showWelcomeWindow)
   bei Docker.Core.TaskQueue.<.ctor>b__16_0()

It seems like some arguments to start the MobyLinuxVM are parsed or passed in a wrong way.
Restarting multiple times did not solve the problem.

I am not sure if this problem is also part of:

• Kitematic setup error: connect ENOENT //./pipe/docker_engine - if I try to start Kitematic the Error: connect ENOENT //./pipe/docker_engine appear, but this should be a symptom and not the cause.
• Docker fails to start on Windows 10 - seems to be similar but I get a different error within log files. If it's needed this issue can be merged.

Expected behavior

Launch installed Kitematic.
By default, Docker Toolbox installs it in C:\Program Files\Docker Toolbox\kitematic

Actual behavior

Ask to install Kitematic

Information

• Diagnostic ID: 63FC49AC-136A-4694-8FC1-E651A239AEE3/2016-08-02_13-35-11
• Windows 10 Pro

Steps to reproduce the behavior

1. Install Docker for Windows & Docker Toolbox
2. Run Kitematic from Docker for Windows (right click in systray icon + "Open Kitematic..."

Expected behavior

Run hello-world image

Actual behavior

C:\Apps>docker run hello-world
Unable to find image 'hello-world:latest' locally
Pulling repository docker.io/library/hello-world
docker: Error while pulling image: Get https://index.docker.io/v1/repositories/library/hello-world/images: x509: certificate signed by unknown authority.
See 'docker run --help'.

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  19836E58-CDE9-4E0B-99A2-79D2A3798817/2016-08-04_14-06-22

Steps to reproduce the behavior

The behavior seems related with the interaction between docker and our corporate proxy.

1. Install Docker 1.12 on Windows
2. Configure corporate proxy
3. Restart docker
4. docker run hello-world

Expected behavior

MobyLinuxVM starts and allows Docker to run successfully.

Actual behavior

Docker crashes, error states that MobyLinuxVM failed to start, because one of the Hyper-V components is not running.
Attempted to start MobyLinuxVM in the Hyper-V manager and it failed presenting the same error.

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  B34992D5-8A0F-4444-B97E-799CE74D37C0/2016-07-29_20-17-51
• host distribution and version (Windows version, build number, etc)
  Edition: Windows 10 Pro
  Version: OS Build: 10586.494
  Processor: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
  Installed Ram: 16.0 GB
  Note: Windows is currently not activated. Would this cause the issue?

Steps to reproduce the behavior

1. Install Docker for Windows
2. Restart Computer
3. Docker attempts to start on startup and fails.

Expected behavior

$ docker-compose --version
docker-compose version 1.x.x-rc-xx, build xxxxxxx

Actual behavior

$ docker-compose --version
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "compose\cli\main.py", line 58, in main
  File "compose\cli\main.py", line 89, in dispatch
  File "compose\cli\docopt_command.py", line 25, in parse
  File "compose\cli\docopt_command.py", line 12, in docopt_full_help
  File "site-packages\docopt.py", line 575, in docopt
  File "site-packages\docopt.py", line 484, in extras
LookupError: unknown encoding: cp65001
docker-compose returned -1

Information

• ID 28C8317A-5C2F-4BC9-AA3B-D47229AA1776/2016-08-02_21-42-43
• Docker version 1.12.0, build 8eab29e, experimental
• Windows 10 Insider Preview Build 14393

Steps to reproduce the behavior

1. Install docker for windows beta), test docker-compose --version
2. Reset to factory defaults
3. Follow instructions at https://docs.docker.com/docker-for-windows/
4. Note that both docker --version and docker-machine --version work

Expected behavior

After docker-update I expect that all images and container are still there.

Actual behavior

After docker-update all my docker-containers and images seem to be gone ("docker ps -a" and "docker images" show nothing).

Information

• A20E5259-982A-4F12-B301-CD5CE7FFCE26/2016-07-29_14-06-39
• I updated to version 1.12.0-beta21 (build 5971)
• There was the question if I wanted to copy the images and container from a previously installed docker named "default". This question I answered with yes

Windows-Info:
Betriebsystemname Microsoft Windows 10 Pro
Version 10.0.14393 Build 14393
Systemtyp x64-basierter PC
Prozessor Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz, 4001 MHz, 4 Kern(e), 8 logische(r) Prozessor(en)
BIOS-Version/-Datum American Megatrends Inc. P1.70, 16.09.2014
SMBIOS-Version 2.8
Version des eingebetteten Controllers 255.255
Hauptplatinenhersteller ASRock
Hardwareabstraktionsebene Version = "10.0.14393.0"
Benutzername IBEOS01\ingo

Expected behavior

Should connect to docker.io/library/hello-world, download the image and run it

Actual behavior

Network times out

Information

• A diagnostic was uploaded with id: C83DC67F-0792-40A5-9882-F6F60EE44A9F/2016-08-01_13-46-15
• Windows 10, Version 1511, OS build 10586.494
  
• Tried with DNS Server set to automatic and fix at 8.8.8.8
• Running on MacBook Pro hardware
• Same result with Docker on the Beta channel

Steps to reproduce the behavior

1. Ensure Hyper-V is installed and running
2. Install Docker for windows
3. Open powershell and type docker run hello-world

Expected behavior

When trying to login to an internal docker registry with:
docker login -u docker-user -p ***** docker-rep.dep.ca.inet:18443

Expected successful login acknowledged with the message
"Login Succeeded"

The exact same command run successfully from a Linux host.

Actual behavior

Error response from daemon: Get https://docker-rep.dep.ca.inet:18443/v1/users/: dial tcp: lookup docker-rep.dep.ca.inet on 192.168.65.3:53: read udp 192.168.65.2:45051->192.168.65.3:53: i/o timeout

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  • 19836E58-CDE9-4E0B-99A2-79D2A3798817/2016-08-05_12-52-45
• host distribution and version (Windows version, build number, etc)
  • Docker 1.12
  • Windows 10, version 1511 (OS version 10586.494)

Steps to reproduce the behavior

1. Added CA certificates for the registry host under C:\ProgramData\Docker\certs.d\docker-rep.dep.ca.inet
2. Restarted Docker
3. docker login -u docker-user -p ***** docker-rep.dep.ca.inet:18443

Expected behavior

I want to disable DOCKER_TLS_VERIFY by adding "DOCKER_TLS_VERIFY": false to docker daemon configuration file

Actual behavior

Dacker failed to start

Information

Win10 ver 1607
Docker 1.12: 5968

I use "docker run -v" mount windows folder , it's successful ,but I ls the Dir , it's empty.
This is my docker for Win10 version and docker info :
Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:15:28 2016
OS/Arch: windows/amd64

Server:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:15:28 2016
OS/Arch: linux/amd64

Containers: 15
Running: 1
Paused: 0
Stopped: 14
Images: 34
Server Version: 1.12.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 103
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.95 GiB
Name: moby
ID: HCJB:ANCS:IOQE:NRMO:NHJR:7VWF:XEGA:QS6E:5YDE:JXNQ:K6CM:A7OW
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
127.0.0.0/8

Docker client for windows used this config:
The setting option , Shared Drives table select c: d: and input my user password.
II am very confused, hope to get your help, thank you.

Expected behavior

Start Docker after default installation, Docker icon shouldnot be red with error message box

Actual behavior

An error window is showing with:
"An Error Occured"
Unable to remove from the database. Exit code: 1
at Docker.Core.Pipe.NamedPipeClient.TrySend(String action, Object[] parameters)
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
at Docker.Core.Backend.BackendClient.Start(Settings settings)
at Docker.Actions.DoStart(Settings settings, Boolean showWelcomeWindow)
at Docker.Core.TaskQueue.<.ctor>b__16_0()

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  08647C6E-0023-4479-80E3-E92D30949DBF/2016-08-03_22-08-36
• a reproducible case if this is a bug, Dockerfiles FTW
  Just start "Docker for Windows"
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)
  Windows Version: Windows 10 Pro Build 10586.
  PSVersion 5.0.10586.494

Steps to reproduce the behavior

1. Fresh install Docker for Windows
2. Run it right after installation

Log

[22:07:49.330][Program ][Info ] Version: 1.12.0-stable
[22:07:49.345][Program ][Info ] Starting on: 8/3/2016 10:07:49 PM
[22:07:49.345][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[22:07:49.345][Program ][Info ] OS: Windows 10 Pro
[22:07:49.345][Program ][Info ] Edition: Professional
[22:07:49.361][Program ][Info ] Id: 1511
[22:07:49.361][Program ][Info ] Build: 10586
[22:07:49.361][Program ][Info ] BuildLabName: 10586.494.amd64fre.th2_release_sec.160630-1736
[22:07:49.361][Program ][Info ] Sha1: 9cd1dc28d3ac81cb5177ff9728f65200304b36f6
[22:07:49.361][Program ][Info ] You can send feedback, including this log file, at https://github.com/docker/for-win/issues
[22:07:49.630][TrackingStatus ][Info ] Crash report and usage statistics are enabled
[22:07:49.646][Mixpanel ][Info ] Id: 08647C6E-0023-4479-80E3-E92D30949DBF
[22:07:49.677][Mixpanel ][Info ] Usage Statistic: appLaunched
[22:07:50.296][NamedPipeClient][Info ] Sending Version()...
[22:07:50.308][NamedPipeClient][Info ] Received response for Version
[22:07:50.312][Mixpanel ][Info ] Usage Statistic: heartbeat
[22:07:45.352][BackendServer ][Info ] Started
[22:07:50.302][NamedPipeServer][Info ] Version()
[22:07:50.305][NamedPipeServer][Info ] Version done.
[22:07:50.774][Notifications ][Info ] Docker is starting...
[22:07:50.775][Updater ][Info ] Checking for updates on channel Stable...
[22:07:50.789][NamedPipeClient][Info ] Sending Stop()...
[22:07:50.793][NamedPipeServer][Info ] Stop()
[22:07:50.796][HyperV ][Info ] Stop
[22:07:50.803][PowerShell ][Info ] Run script with parameters: -Stop True...
[22:07:52.134][Updater ][Info ] Local build 5968 is as good as the remote 5968 on channel Stable
[22:07:53.079][HyperV ][Info ] VM MobyLinuxVM does not exist
[22:07:53.090][NamedPipeClient][Info ] Received response for Stop
[22:07:53.087][NamedPipeServer][Info ] Stop done.
[22:07:53.093][NamedPipeClient][Info ] Sending Start(Docker.Core.Settings)...
[22:07:53.099][NamedPipeServer][Info ] Start(Docker.Core.Settings)
[22:07:53.102][HyperVGuids ][Info ] Installing GUIDs...
[22:07:53.105][HyperVGuids ][Info ] GUIDs installed
[22:07:53.110][Firewall ][Info ] Opening ports for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe...
[22:07:53.707][Firewall ][Info ] Ports are opened
[22:07:53.711][HyperV ][Info ] Create
[22:07:53.714][PowerShell ][Info ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso...
[22:07:54.303][HyperV ][Info ] Enabled workaround for Build 10586 VMSwitch issue
[22:07:57.036][HyperV ][Info ] Creating Switch: DockerNAT...
[22:07:57.938][HyperV ][Info ] VMSwitch (Name = 'DockerNAT') [Id = 'c64d4856-87cf-458d-b640-6cf592e21510']
[22:07:58.069][HyperV ][Info ] Switch created.
[22:07:58.524][HyperV ][Info ] Set IP address on switch
[22:07:59.771][HyperV ][Info ] Creating dynamic VHD: C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\MobyLinuxVM.vhdx
[22:08:00.843][HyperV ][Info ] Creating VM MobyLinuxVM...
[22:08:02.740][HyperV ][Info ] VM created.
[22:08:02.747][DataKit ][Info ] Starting...
[22:08:02.751][PowerShell ][Info ] Run script...
[22:08:02.799][DataKit ][Info ] Started
[22:08:02.799][VpnKit ][Info ] Starting...
[22:08:02.799][PowerShell ][Info ] Run script...
[22:08:02.831][VpnKit ][Info ] Started
[22:08:02.831][ApiProxy ][Info ] Starting...
[22:08:02.831][DataKit ][Info ]
[22:08:02.831][DataKit ][Info ] +6248us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:02.831][PowerShell ][Info ] Run script...
[22:08:02.846][VpnKit ][Info ] com.docker.slirp.exe: Logging to stdout (stdout:true DEBUG:false)
[22:08:02.862][VpnKit ][Info ] com.docker.slirp.exe: Setting handler to ignore all SIGPIPE signals
[22:08:02.862][VpnKit ][Info ] com.docker.slirp.exe: vpnkit version %VERSION% with hostnet version local %HOSTNET_PINNED% uwt version 0.0.3 hvsock version 0.10.0 %HVSOCK_PINNED%
[22:08:02.862][VpnKit ][Info ] com.docker.slirp.exe: starting port_forwarding port_control_url:hyperv-connect://b5bfc827-7d55-49de-8a3c-1803d284ef65 max_connections:None vsock_path:
[22:08:02.862][VpnKit ][Info ] com.docker.slirp.exe: connecting to b5bfc827-7d55-49de-8a3c-1803d284ef65:0B95756A-9985-48AD-9470-78E060895BE7
[22:08:02.862][ApiProxy ][Info ] Started
[22:08:02.877][VpnKit ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://b5bfc827-7d55-49de-8a3c-1803d284ef65
[22:08:02.877][VpnKit ][Warning] com.docker.slirp.exe: no database: using hardcoded network configuration values
[22:08:02.877][VpnKit ][Info ] com.docker.slirp.exe: connecting to b5bfc827-7d55-49de-8a3c-1803d284ef65:30D48B34-7D27-4B0B-AAAF-BBBED334DD59
[22:08:02.877][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/exclude
[22:08:02.900][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/http
[22:08:02.900][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/https
[22:08:02.896][VpnKit ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://b5bfc827-7d55-49de-8a3c-1803d284ef65
[22:08:02.900][ApiProxy ][Info ] docker proxy (on deprecated port): ready
[22:08:02.900][ApiProxy ][Info ] dns server: ready
[22:08:02.919][ApiProxy ][Info ] docker proxy: ready
[22:08:02.971][DataKit ][Info ] Restarting...
[22:08:03.179][PowerShell ][Info ] Run script...
[22:08:03.196][DataKit ][Info ] Restarted
[22:08:03.218][DataKit ][Info ]
[22:08:03.222][DataKit ][Info ] +3934us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:03.315][DataKit ][Info ] Restarting...
[22:08:03.520][PowerShell ][Info ] Run script...
[22:08:03.536][DataKit ][Info ] Restarted
[22:08:03.561][DataKit ][Info ]
[22:08:03.564][DataKit ][Info ] +5888us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:03.654][DataKit ][Info ] Restarting...
[22:08:03.859][PowerShell ][Info ] Run script...
[22:08:04.138][Database ][Error ] 2016/08/03 22:08:02 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:03 Failed to contact the database on .\pipe\dockerDataBase: open .\pipe\dockerDataBase: The system cannot find the file specified.

[22:08:04.141][Database ][Error ] Unable to write to the database: Unable to remove from the database. Exit code: 1. Let's retry in 1s
[22:08:04.149][DataKit ][Info ] Restarted
[22:08:04.171][DataKit ][Info ]
[22:08:04.175][DataKit ][Info ] +3875us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:04.265][DataKit ][Info ] Restarting...
[22:08:04.471][PowerShell ][Info ] Run script...
[22:08:04.487][DataKit ][Info ] Restarted
[22:08:04.509][DataKit ][Info ]
[22:08:04.513][DataKit ][Info ] +3927us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:04.610][DataKit ][Info ] Restarting...
[22:08:04.814][PowerShell ][Info ] Run script...
[22:08:04.832][DataKit ][Info ] Restarted
[22:08:04.853][DataKit ][Info ]
[22:08:04.857][DataKit ][Info ] +3895us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:04.962][DataKit ][Info ] Restarting...
[22:08:05.145][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/exclude
[22:08:05.148][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/http
[22:08:05.151][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/https
[22:08:05.197][PowerShell ][Info ] Run script...
[22:08:06.379][Database ][Error ] 2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:05 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:06 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:06 Failed to contact the database on .\pipe\dockerDataBase: open .\pipe\dockerDataBase: The system cannot find the file specified.

[22:08:06.383][Database ][Error ] Unable to write to the database: Unable to remove from the database. Exit code: 1. Let's retry in 1s
[22:08:06.393][DataKit ][Info ] Restarted
[22:08:06.417][DataKit ][Info ]
[22:08:06.420][DataKit ][Info ] +4220us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:06.512][DataKit ][Info ] Restarting...
[22:08:06.720][PowerShell ][Info ] Run script...
[22:08:06.737][DataKit ][Info ] Restarted
[22:08:06.759][DataKit ][Info ]
[22:08:06.763][DataKit ][Info ] +3976us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:06.867][DataKit ][Info ] Restarting...
[22:08:07.073][PowerShell ][Info ] Run script...
[22:08:07.091][DataKit ][Info ] Restarted
[22:08:07.116][DataKit ][Info ]
[22:08:07.119][DataKit ][Info ] +4314us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:07.220][DataKit ][Info ] Restarting...
[22:08:07.387][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/exclude
[22:08:07.391][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/http
[22:08:07.394][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/https
[22:08:07.425][PowerShell ][Info ] Run script...
[22:08:08.620][Database ][Error ] 2016/08/03 22:08:07 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:07 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:07 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:07 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:07 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:07 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:08 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:08 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:08 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:08 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:08 Failed to contact the database on .\pipe\dockerDataBase: open .\pipe\dockerDataBase: The system cannot find the file specified.

[22:08:08.624][Database ][Error ] Unable to write to the database: Unable to remove from the database. Exit code: 1. Let's retry in 1s
[22:08:08.639][DataKit ][Info ] Restarted
[22:08:08.663][DataKit ][Info ]
[22:08:08.667][DataKit ][Info ] +4211us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:08.690][DataKit ][Info ] Restarting...
[22:08:08.895][PowerShell ][Info ] Run script...
[22:08:08.912][DataKit ][Info ] Restarted
[22:08:08.935][DataKit ][Info ]
[22:08:08.938][DataKit ][Info ] +3903us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:09.035][DataKit ][Info ] Restarting...
[22:08:09.241][PowerShell ][Info ] Run script...
[22:08:09.258][DataKit ][Info ] Restarted
[22:08:09.281][DataKit ][Info ]
[22:08:09.284][DataKit ][Info ] +4084us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:09.373][DataKit ][Info ] Restarting...
[22:08:09.579][PowerShell ][Info ] Run script...
[22:08:09.595][DataKit ][Info ] Restarted
[22:08:09.620][DataKit ][Info ]
[22:08:09.624][DataKit ][Info ] +5583us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:09.629][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/exclude
[22:08:09.632][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/http
[22:08:09.637][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/https
[22:08:09.719][DataKit ][Info ] Restarting...
[22:08:09.924][PowerShell ][Info ] Run script...
[22:08:10.472][DataKit ][Info ] Restarted
[22:08:10.494][DataKit ][Info ]
[22:08:10.498][DataKit ][Info ] +3949us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:10.588][DataKit ][Info ] Restarting...
[22:08:10.795][PowerShell ][Info ] Run script...
[22:08:10.825][DataKit ][Info ] Restarted
[22:08:10.851][DataKit ][Info ]
[22:08:10.854][DataKit ][Info ] +4322us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:10.863][Database ][Error ] 2016/08/03 22:08:09 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:09 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:09 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:09 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:10 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:10 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:10 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:10 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:10 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:10 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:10 Failed to contact the database on .\pipe\dockerDataBase: open .\pipe\dockerDataBase: The system cannot find the file specified.

[22:08:10.866][Database ][Error ] Unable to write to the database: Unable to remove from the database. Exit code: 1. Let's retry in 1s
[22:08:10.943][DataKit ][Info ] Restarting...
[22:08:11.148][PowerShell ][Info ] Run script...
[22:08:11.165][DataKit ][Info ] Restarted
[22:08:11.188][DataKit ][Info ]
[22:08:11.191][DataKit ][Info ] +3940us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:11.279][DataKit ][Info ] Restarting...
[22:08:11.488][PowerShell ][Info ] Run script...
[22:08:11.523][DataKit ][Info ] Restarted
[22:08:11.570][DataKit ][Info ]
[22:08:11.576][DataKit ][Info ] +8158us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:11.681][DataKit ][Info ] Restarting...
[22:08:11.870][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/exclude
[22:08:11.876][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/http
[22:08:11.882][Database ][Info ] Removing com.docker.driver.amd64-linux/proxy/https
[22:08:11.887][PowerShell ][Info ] Run script...
[22:08:11.912][DataKit ][Info ] Restarted
[22:08:11.936][DataKit ][Info ]
[22:08:11.939][DataKit ][Info ] +4399us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:12.030][DataKit ][Info ] Restarting...
[22:08:12.236][PowerShell ][Info ] Run script...
[22:08:12.269][DataKit ][Info ] Restarted
[22:08:12.313][DataKit ][Info ]
[22:08:12.320][DataKit ][Info ] +7992us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:12.424][DataKit ][Info ] Restarting...
[22:08:12.630][PowerShell ][Info ] Run script...
[22:08:12.663][DataKit ][Info ] Restarted
[22:08:12.699][DataKit ][Info ]
[22:08:12.704][DataKit ][Info ] +5305us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:12.794][DataKit ][Info ] Restarting...
[22:08:12.999][PowerShell ][Info ] Run script...
[22:08:13.019][DataKit ][Info ] Restarted
[22:08:13.043][DataKit ][Info ]
[22:08:13.047][DataKit ][Info ] +4130us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:13.070][DataKit ][Info ] Restarting...
[22:08:13.120][Database ][Error ] 2016/08/03 22:08:11 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Retry dialing .\pipe\dockerDataBase in 100ms
2016/08/03 22:08:12 Failed to contact the database on .\pipe\dockerDataBase: open .\pipe\dockerDataBase: The system cannot find the file specified.

[22:08:13.126][NamedPipeServer][Error ] Unable to execute Start: Unable to remove from the database. Exit code: 1 at Docker.Backend.Database.RemoveKeys(String[] keys)
at Docker.Backend.Database.TryWrite(Settings settings)
at Docker.Backend.Database.Write(Settings settings)
at Docker.Backend.Backend.Start(Settings settings)
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass7_0.b__0(Object[] parameters)
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)
[22:08:13.137][NamedPipeClient][Error ] Unable to send Start: Unable to remove from the database. Exit code: 1
[22:08:13.144][NamedPipeClient][Info ] Sending CheckInstallation()...
[22:08:13.149][NamedPipeServer][Info ] CheckInstallation()
[22:08:13.156][HyperV ][Info ] Check Hyper-V Windows optional feature
[22:08:13.162][PowerShell ][Info ] Run script...
[22:08:13.276][PowerShell ][Info ] Run script...
[22:08:13.867][HyperV ][Info ] Hyper-V Windows feature is enabled
[22:08:13.879][NamedPipeClient][Info ] Received response for CheckInstallation
[22:08:13.872][NamedPipeServer][Info ] CheckInstallation done.
[22:08:13.885][NamedPipeClient][Info ] Sending CheckHyperVState()...
[22:08:13.889][DataKit ][Info ] Restarted
[22:08:13.894][NamedPipeServer][Info ] CheckHyperVState()
[22:08:13.899][HyperV ][Info ] Check Hyper-V State
[22:08:13.905][PowerShell ][Info ] Run script with parameters: -Check True...
[22:08:13.915][DataKit ][Info ]
[22:08:13.922][DataKit ][Info ] +5518us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:14.021][DataKit ][Info ] Restarting...
[22:08:14.228][PowerShell ][Info ] Run script...
[22:08:14.468][HyperV ][Info ] Hyper-V is running
[22:08:14.479][NamedPipeClient][Info ] Received response for CheckHyperVState
[22:08:14.474][NamedPipeServer][Info ] CheckHyperVState done.
[22:08:14.486][Notifications ][Error ] Unable to remove from the database. Exit code: 1
[22:08:14.483][DataKit ][Info ] Restarted
[22:08:14.507][DataKit ][Info ]
[22:08:14.515][DataKit ][Info ] +4291us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:14.622][DataKit ][Info ] Restarting...
[22:08:14.829][PowerShell ][Info ] Run script...
[22:08:14.848][DataKit ][Info ] Restarted
[22:08:14.872][DataKit ][Info ]
[22:08:14.878][DataKit ][Info ] +4009us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:14.971][DataKit ][Info ] Restarting...
[22:08:15.177][PowerShell ][Info ] Run script...
[22:08:15.195][DataKit ][Info ] Restarted
[22:08:15.216][DataKit ][Info ]
[22:08:15.221][DataKit ][Info ] +3883us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:15.309][DataKit ][Info ] Restarting...
[22:08:15.516][PowerShell ][Info ] Run script...
[22:08:15.551][DataKit ][Info ] Restarted
[22:08:15.593][DataKit ][Info ]
[22:08:15.600][DataKit ][Info ] +5059us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:15.595][DataKit ][Info ] com.docker.db.exe: internal error, uncaught exception:
[22:08:15.610][DataKit ][Info ] Unix.Unix_error(40, "select", "")
[22:08:15.615][DataKit ][Info ]
[22:08:15.802][DataKit ][Info ] Restarting...
[22:08:16.018][PowerShell ][Info ] Run script...
[22:08:16.053][DataKit ][Info ] Restarted
[22:08:16.087][DataKit ][Info ]
[22:08:16.093][DataKit ][Info ] +5068us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:16.195][DataKit ][Info ] Restarting...
[22:08:16.402][PowerShell ][Info ] Run script...
[22:08:16.424][DataKit ][Info ] Restarted
[22:08:16.450][DataKit ][Info ]
[22:08:16.455][DataKit ][Info ] +4676us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:16.476][DataKit ][Info ] Restarting...
[22:08:16.683][PowerShell ][Info ] Run script...
[22:08:16.718][DataKit ][Info ] Restarted
[22:08:16.748][DataKit ][Info ]
[22:08:16.753][DataKit ][Info ] +4404us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:16.844][DataKit ][Info ] Restarting...
[22:08:17.050][PowerShell ][Info ] Run script...
[22:08:17.076][DataKit ][Info ] Restarted
[22:08:17.100][DataKit ][Info ]
[22:08:17.104][DataKit ][Info ] +3902us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:17.215][DataKit ][Info ] Restarting...
[22:08:17.422][PowerShell ][Info ] Run script...
[22:08:17.453][DataKit ][Info ] Restarted
[22:08:17.482][DataKit ][Info ]
[22:08:17.486][DataKit ][Info ] +5021us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:17.585][DataKit ][Info ] Restarting...
[22:08:17.800][PowerShell ][Info ] Run script...
[22:08:17.825][DataKit ][Info ] Restarted
[22:08:17.851][DataKit ][Info ]
[22:08:17.854][DataKit ][Info ] +3849us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:17.943][DataKit ][Info ] Restarting...
[22:08:18.148][PowerShell ][Info ] Run script...
[22:08:18.181][DataKit ][Info ] Restarted
[22:08:18.216][DataKit ][Info ]
[22:08:18.220][DataKit ][Info ] +4828us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:18.308][DataKit ][Info ] Restarting...
[22:08:18.514][PowerShell ][Info ] Run script...
[22:08:18.546][DataKit ][Info ] Restarted
[22:08:18.577][DataKit ][Info ]
[22:08:18.581][DataKit ][Info ] +4627us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:18.672][DataKit ][Info ] Restarting...
[22:08:18.877][PowerShell ][Info ] Run script...
[22:08:18.912][DataKit ][Info ] Restarted
[22:08:18.956][DataKit ][Info ]
[22:08:18.963][DataKit ][Info ] +7966us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:19.076][DataKit ][Info ] Restarting...
[22:08:19.282][PowerShell ][Info ] Run script...
[22:08:19.304][DataKit ][Info ] Restarted
[22:08:19.332][DataKit ][Info ]
[22:08:19.336][DataKit ][Info ] +5143us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:19.423][DataKit ][Info ] Restarting...
[22:08:19.633][PowerShell ][Info ] Run script...
[22:08:19.665][DataKit ][Info ] Restarted
[22:08:19.693][DataKit ][Info ]
[22:08:19.697][DataKit ][Info ] +4680us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:19.787][DataKit ][Info ] Restarting...
[22:08:19.992][PowerShell ][Info ] Run script...
[22:08:20.009][DataKit ][Info ] Restarted
[22:08:20.031][DataKit ][Info ]
[22:08:20.034][DataKit ][Info ] +3964us Datakit Starting com.docker.db.exe 16bb469 ...
[22:08:20.121][DataKit ][Info ] Restarting...
[22:08:20.229][ErrorReportWindow][Info ] Open logs

Hi,
First, thanks for your work, I've seen a great demo at DevoxxFR and I can't wait to use it :)

I'm running Docker for Windows Version: 1.12.0-beta21 on a WIN10 VM.
Hyper-V is activated and Windows services are OK.
The MobyLinuxVM is well created but Docker fails to start because it cannot get an IP for the VM.

The DNS server radio button configuration is set to "automatic".
I've tried to reboot, reset to factory, uninstall/reinstall,
I've also tried to set the a fixed DNS.

Error :
Failed to start VM "MobyLinuxVM": The VM couldn't get an IP address after 60 tries
at Docker.Core.Pipe.NamedPipeClient.TrySend(String action, Object[] parameters)
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
at Docker.Core.Backend.BackendClient.Start(Settings settings)
at Docker.Actions.DoStart(Settings settings, Boolean showWelcomeWindow)
at Docker.Core.TaskQueue.<.ctor>b__16_0()

Diagnostic id :
5C73F6A7-06A7-40B5-A2F9-9EF5214B83F2/2016-08-02_09-22-49

Expected behavior

Using/connect Kitematic to run Docker containers.

Actual behavior

When opening Kitematic an error occurs at 99% of the initial setup. Error message: connect TIMED OUT 198.105.244.23:2375.

Information

• Diagnostic ID: 3D05AAEF-630B-4F46-A82E-D9A6415A59F9/2016-07-29_09-10-02
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• Windows 10, Docker ver: 1.12.0-beta21 (build: 5971) 5b59d37

Steps to reproduce the behavior

1. Docker running.
2. Start Kitematic. (e.g. right click on Docker in system tray & open Kitematic)

Copy from https://forums.docker.com/t/locahost-only-bind/18622

With the new docker for windows version(beta 20 build 5779), it binds to localhost only, but I don't think that is a good idea for windows because certain ports are blocked for example 445, 80

Expected behavior

samba

Actual behavior

Error response from daemon: driver failed programming external connectivity on endpoint samba (43a4e1ec467d6f584d5799e7ed3b333bd2bcabc17f0086ec0851024b018620bc): Error starting userland proxy: Bind for 0.0.0.0:445: unexpected error Unix.Unix_error(Unix.EACCES, "bind", "")
Error: failed to start containers: samba

Information

• Windows 10 professional, docker for windows beta 20 build 5779

Steps to reproduce the behavior

1. docker run -it -p 139:139 -p 445:445 -d dperson/samba

Expected behavior

be able to write to a volume in windows.

Actual behavior

no write privilege

Information

E9C6CB2E-BD24-4E1B-9A89-F55DD8093E0B/2016-08-10_09-19-31

• Diagnostic ID from "Diagnose & Feedback" in the menu.
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)

Steps to reproduce the behavior

1. Take any working Dockerfile or docker-compose file that requires a host volume on windows
2. run the image with -v settings eg docker run --rm -v c:/Users:/data alpine ls /data and there is either no listing shown or only a subset of the available file.

I have read every comment and suggestion, on the boards, including firewall, checking the credentials for the drive sharing, changing the virtual network card to be a private network, etc etc. It all worked 2 days ago and I have made no changes to my docker configurations.
Windows is 10.0.1.14393 Build 14393
Docker is Version 1.12.0-beta21 (build: 5971) 5b59d37

Expected behavior

Docker starts after installation normally

Actual behavior

Docker is stuck at "Docker is starting..."

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu is not possible, button doesn't seem to be working.
• Log file excerpt:

[21:15:13.801][DataKit        ][Info   ] +399626us       fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[21:15:13.800][Database       ][Info   ] Writing com.docker.driver.amd64-linux/native/port-forwarding=true
[21:15:14.777][DataKit        ][Info   ] 
[21:15:14.777][DataKit        ][Info   ] +1377411us       fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[21:15:14.778][Database       ][Info   ] Successfully wrote 9 value(s)
[21:15:14.779][HyperV         ][Info   ] Start
[21:15:14.780][PowerShell     ][Info   ] Run script with parameters: -Start True...
[21:15:14.841][HyperV         ][Info   ] Starting VM MobyLinuxVM...

The program then gets stuck after that and nothing happens (waited for 30 mins)

Steps to reproduce the behavior

1. Install Docker on windows (Version: 1.12.0-stable)
2. Wait for Docker to start (tray icon: "Docker is starting..."

Are there any plans to release source, at least for the MobyLinuxVM portion?

I've been unable to use this at work due to our SSL inspection proxy. With Toolbox I was able to build a custom boot2docker.iso that has the root CA certificates added and sets the proxy environment variables appropriately.

Expected behavior

docker pull works

Actual behavior

docker pull does not work

ERROR: Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/redis/images. You may want to check your internet connection or if you are behind a proxy.

Information

Steps to reproduce the behavior

1. docker pull any-image

I have a docker compose file that is a mix of image based services and built services (using build). When I run the docker-compose up on my Ubuntu linux box everything works properly. However running docker-compose up on my WIndows 10 box my built services can't perform name resolution to the image based services.

Expected behavior

I have a Zookeeper (zoo1) service, Kafka (streams1), and my application (ingest1). zoo1 and streams1 are services configured with images. When they start up they communicate just fine with each other. I expect that when I start up ingest1 it will be able to resolve the address of zoo1 properly.

Actual behavior

On Docker for Windows, the ingest1 box gets an invalid IP address for zoo1.

Information

Here is my docker-compose.yml file:

version: '2'
services:
    zoo1:
        image: xxxxx/zookeeper-test
        ports:
            - "2181:2181"
    streams1:
        image: xxxxxxx/kafka
        ports:
            - "9092:9092"
            - "9010:9010"
        links:
            - zoo1
        environment:
            KAFKA_ZOOKEEPER_CONNECT: "zoo1:2181"
            KAFKA_ADVERTISED_HOST_NAME: "streams1"
            KAFKA_ADVERTISED_PORT: "9092"
            KAFKA_CREATE_TOPICS: "pipeline:1:1,logs:1:1"
            JMX_PORT: "9010"

    ingest1:
        build: 
            context: .
            dockerfile: ./pipeline/stages/ingestion/Dockerfile
        ports:
            - "8080:8080"
        links: 
            - zoo1
            - streams1
        environment:
            ZOOKEEPER_CONNECT: "zoo1:2181"
        restart: "on-failure:10"

Here is part of the output of docker network insepct for my network:

    {
        "Name": "naveego_default",
        "Id": "14d50fc7702025cb6e8d79f390d224d02f3b5bf6070bb572bc344c11637bd083",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.18.0.0/16",
                    "Gateway": "172.18.0.1/16"
                }
            ]
        },
        "Internal": false,

This is the log file from ingest1:

ingest1_1       | time="2016-08-22T00:43:23Z" level=debug msg="Connecting to configuration servers: zoo1:2181"
ingest1_1       | 2016/08/22 00:43:25 Failed to connect to 198.105.254.24:2181: dial tcp 198.105.254.24:2181: i/o timeout
ingest1_1       | 2016/08/22 00:43:26 Failed to connect to 198.105.244.24:2181: dial tcp 198.105.244.24:2181: i/o timeout
ingest1_1       | time="2016-08-22T00:43:26Z" level=fatal msg="Error reading configurationzk: could not connect to a server"

I should be getting an address in the same network (i.e. 172.18.0.x).

Note: I have another container that is being built in the file and I get the same result.

Why aren't my built services able to use name resolution?

Expected behavior

When the Docker for Windows application is started a VM should be created in Hyper-V.

Actual behavior

Upon starting the application nothing seemingly happens. This is confirmed by the log file seen here: http://pastebin.com/keXwv0r0.
I have let the application run for 10 minutes without any changes to the log file. From the task manager I can confirm that both Docker.Service and Docker for Windows are running. In the Hyper-V manager I can also see that no VM and no virtual switch is created. This indicates to me that the powershell script(docker/resources/MobyLinux.ps1) that is supposed to run when starting up the program is not initiated.
I've attempted to both disable and enable Hyper-V. I've also reinstalled Docker (both stable and beta) several times.

Information

Diagnostic ID: 9F8E4BB9-3CAA-4F23-AB78-DDEC90843FD8
Docker version: 1.12.0
Log file: http://pastebin.com/keXwv0r0
OS: Windows 10 Pro 1511
OS Build: 10586.494

Steps to reproduce the behavior

1. Enable Hyper-V
2. Install Docker
3. Start Docker

Expected behavior

Actual behavior

During and since upgrade to version 1.12.0-beta21 (build 5971) 5b59d37
I get the error "Inconsistent parameters PolicyStore PersistentStore and Dhcp Enabled."
I am not aware of having changed any settings from the defaults.
The docker symbol displayed red on each restart.

The error did resolve itself after 3-4 times of restarting docker. Now everything seems to be fine.

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  6C337D1E-D334-4D53-814C-2B9AC9419A20/2016-07-29_02-40-36

Steps to reproduce the behavior

Agree to the automatic update to version 1.12.0-beta21 in Docker for Windows.

Does Docker for Windows support CUDA? And can I find the gpu device on Docker?

Thanks & Regards.

Expected behavior

I should be able to use a registry signed by a custom Certificate Authority without having to register it as insecure.

Actual behavior

When attempting to use a registry signed by a custom Certificate Authority Docker for Windows returns a x509: certificate signed by unknown authority error. Only workaround is to register registry as insecure.

Related to #26, #36, #23, & docker/for-mac#343. Per @friism at #9 (comment) looks like something like this may already be on the roadmap.

BUG REPORT INFORMATION

Output of docker version:

Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      linux/amd64

Output of docker info:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 8
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null overlay host
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.952 GiB
Name: moby
ID: 2DM3:KRR3:3SSK:BFOE:TQQO:BAO2:RQFO:6QEK:UNVN:M3MM:EKLY:LKQE
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
 127.0.0.0/8

Additional environment details (AWS, VirtualBox, physical, etc.):
I use Windows PowerShell

Steps to reproduce the issue:

I've tried to create a folder via docker and binding volume.

Here is my two commands:

• First with E:\Dropbox\Travail\www\docker
• Second with E:/Dropbox/Travail/www/docker

PS E:\Dropbox\Travail\www\docker> docker run --rm -it -v E:\Dropbox\Travail\www\docker:/tmp -w /tmp roukmoute/symfony-installer new test1

  WARNING  Your Symfony Installer version (1.5.6-DEV) is outdated.
 Execute the command "/usr/local/bin/symfony selfupdate" to get the latest version (1.5.8).

 Downloading Symfony...

    5.11 MB/5.11 MB ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓  100%

 Preparing project...

 ✔  Symfony 3.1.3 was successfully installed. Now you can:

    * Change your current directory to /tmp/test1

    * Configure your application in app/config/parameters.yml file.

    * Run your application:
        1. Execute the php bin/console server:run command.
        2. Browse to the http://localhost:8000 URL.

    * Read the documentation at http://symfony.com/doc

PS E:\Dropbox\Travail\www\docker> docker run --rm -it -v E:/Dropbox/Travail/www/docker:/tmp -w /tmp roukmoute/symfony-installer new test2

  WARNING  Your Symfony Installer version (1.5.6-DEV) is outdated.
 Execute the command "/usr/local/bin/symfony selfupdate" to get the latest version (1.5.8).

 Downloading Symfony...

    5.11 MB/5.11 MB ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓  100%

 Preparing project...

 ✔  Symfony 3.1.3 was successfully installed. Now you can:

    * Change your current directory to /tmp/test2

    * Configure your application in app/config/parameters.yml file.

    * Run your application:
        1. Execute the php bin/console server:run command.
        2. Browse to the http://localhost:8000 URL.

    * Read the documentation at http://symfony.com/doc

PS E:\Dropbox\Travail\www\docker> ls
PS E:\Dropbox\Travail\www\docker>

Describe the results you received:
There is no folder.

Describe the results you expected:
Command ls would return test1 and/or test2 folder.

Is it the same thing as #25?

The documentation says:

You can import a default VirtualBox VM after installing Docker for Windows by using the Settings menu in the System Tray.

There doesn't seem to be any option for that in the Settings section.

When I stop the docker service for any reason and then restart it later, it doesn't restart cleanly, so I have to use the "Restart Docker..." button in the GUI

That is, here's my test case:

stop-service com.docker.service
start-service com.docker.service
docker version

Expected behavior

I should be able to stop the docker service, and start it again later, and use it:

Actual behavior

Client:                                                                                                                     
 Version:      1.12.0                                                                                                       
 API version:  1.24                                                                                                         
 Go version:   go1.6.3                                                                                                      
 Git commit:   8eab29e                                                                                                      
 Built:        Thu Jul 28 21:15:28 2016                                                                                     
 OS/Arch:      windows/amd64                                                                                                
An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version: open //./pipe/docker_engine: The system cannot find the file specified. 

Information

A diagnostic was uploaded with id: 26E1532F-8294-4698-98A9-E66F4EFA30EC/2016-08-17_03-44-09

Product version info:

Client:                                    
 Version:      1.12.0                      
 API version:  1.24                        
 Go version:   go1.6.3                     
 Git commit:   8eab29e                     
 Built:        Thu Jul 28 21:15:28 2016    
 OS/Arch:      windows/amd64               

Server:                                    
 Version:      1.12.0                      
 API version:  1.24                        
 Go version:   go1.6.3                     
 Git commit:   8eab29e                     
 Built:        Thu Jul 28 21:15:28 2016    
 OS/Arch:      linux/amd64                 

NOTE: When I try this with the latest dev builds for Windows Containers, that service does start/stop and work, but obviously it only hosts Windows images (and for some reason, will only talk to me if I run docker elevated).

Server:                                    
 Version:      1.13.0-dev                  
 API version:  1.25                        
 Go version:   go1.6.3                     
 Git commit:   4105cff                     
 Built:        Mon Aug 15 18:37:46 2016    
 OS/Arch:      windows/amd64    

Expected behavior

Directory owner can be changed with chown within the container for mounted volumes.

Actual behavior

Using chown within the container for a mounted volume does nothing.

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
• Windows 10 Pro, Docker 1.12.0-beta21 (build 5971) - also tried stable release

Steps to reproduce the behavior

1. C:\Users\sotera>docker run --rm -v c:\users\sotera\docker\sotera:/var/lib/postgresql/data postgres /bin/bash -c "chown postgres:postgres /var/lib/postgresql/data && ls -lh /var/lib/postgresql/"

   total 4.0K drwxr-xr-x 2 root root 4.0K Aug 16 23:29 data

Expected behavior

I would like to connect my dockerized app to ports on my local host, to use development databases, etc.

Actual behavior

I am unable to make any connection to the docker host, either using the container's IP or the gateway IP (e.g. 172.17.0.1).

Information

Docker version 1.12.0, build 8eab29e

I also attempted to create a dedicated bridge subnet using docker network so that I could assign an IP to the container, but I experienced the same results.

I tested using an HTTP server on my host (ASP.NET Core Kestrel server), on the wildcard IP 0.0.0.0 at port 5000, attempting connection with curl. I also tested with Postgres, updating pg_hba.conf with both the wildcard IP and the DockerNAT IP (10.0.75.1 in my case).

Any workarounds would be appreciated.

Steps to reproduce the behavior

1. Create a containerized app (I tried several, but ended up doing most testing with a vanilla Ubuntu image).
2. Expose a service on the host at a specific port (like Postgres on port 5432), ensuring that the listener is listening on the correct IP.
3. Attempt to connect to the port using the container's IP or gateway IP.
4. Should see connection refused

Thanks!

Expected behavior

When I git clone my source repo
And I run the build of that source inside a container with local file system mounted
Then I expect that the build will work

Actual behavior

The build is failing with

ln: failed to create symbolic link '../build/.config': Operation not supported

Information

• 1157C837-2963-4A79-A337-A44A61FC8BEF/2016-08-18_15-43-43
• Windows 10.0.14393

Steps to reproduce the behavior

In powershell

1. git clone <blah>
2. cd <blah> (the Dockerfile lives at the top-level)
3. docker build --tag=<thing> --build-arg USER=${env:username} --build-arg UID=1000 .
4. docker run -u ${env:username} -it -v ${pwd}:/mnt/work octane/fw:latest bash ./build.sh

Not sure if it is relevant, but the reason for building the image and then running, and the reason for the build args is to handle permissions issues that typically occur when running on a Linux host (I'm attempting to enable Windows here). There are corresponding statements in my Dockerfile like this:

# This is to avoid permissions issues with files created during the build
# It assumes the same user is building the image as is running it!
# We use the --gecos option because adduser prompts otherwise and leaves some messy stderr output
ARG USER
ARG UID
RUN adduser --disabled-password --gecos "First Last,RoomNumber,WorkPhone,HomePhone" --uid $UID $USER

Expected behavior

Being able to pull images

Actual behavior

When downloading big images from a local registry (Artifactory 4.11) the pull stops randomly, sometimes shortly after I started the pull, sometimes after few minutes (image is 8.5GB).
I am able to pull smaller images from Artifactory.

Information

• Diagnostic ID
  EFE1F7F6-7085-4DAD-895D-849B3227EBCC/2016-08-08_15-33-53
• host distribution and version (Windows version, build number, etc)
  Docker for Windows, Docker version 1.12.0, build 8eab29e, experimental

Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:04:48 2016
OS/Arch: windows/amd64
Experimental: true

Server:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:04:48 2016
OS/Arch: linux/amd64

Steps to reproduce the behavior

1. docker pull imagename

2. wait for it to hung

Here is the logs I have on my local docker
[15:29:56.917][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input 192.168.65.2:37267-10.0.75.1:53 (DNS[89cc]): shutting down listening thread
[15:30:03.672][VpnKit ][Debug ] com.docker.slirp.exe: ARP responding to: who-has 192.168.65.1?
[15:30:13.251][VpnKit ][Info ] Restarting...
[15:30:13.457][PowerShell ][Info ] Run script...
[15:30:13.513][VpnKit ][Info ] Restarted
[15:30:13.534][VpnKit ][Info ] com.docker.slirp.exe: Logging to stdout (stdout:true DEBUG:false)
[15:30:13.539][VpnKit ][Info ] com.docker.slirp.exe: Setting handler to ignore all SIGPIPE signals
[15:30:13.542][VpnKit ][Info ] com.docker.slirp.exe: vpnkit version %VERSION% with hostnet version local %HOSTNET_PINNED% uwt version 0.0.3 hvsock version 0.10.0 %HVSOCK_PINNED%
[15:30:13.546][VpnKit ][Info ] com.docker.slirp.exe: starting port_forwarding port_control_url:hyperv-connect://f0949704-c9e2-4af9-b2f8-f28d7a8efeef max_connections:None vsock_path:
[15:30:13.549][VpnKit ][Info ] com.docker.slirp.exe: connecting to f0949704-c9e2-4af9-b2f8-f28d7a8efeef:0B95756A-9985-48AD-9470-78E060895BE7
[15:30:13.553][VpnKit ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://f0949704-c9e2-4af9-b2f8-f28d7a8efeef
[15:30:13.557][VpnKit ][Warning] com.docker.slirp.exe: no database: using hardcoded network configuration values
[15:30:13.560][VpnKit ][Info ] com.docker.slirp.exe: connecting to f0949704-c9e2-4af9-b2f8-f28d7a8efeef:30D48B34-7D27-4B0B-AAAF-BBBED334DD59
[15:30:13.564][VpnKit ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://f0949704-c9e2-4af9-b2f8-f28d7a8efeef
[15:30:13.567][VpnKit ][Info ] com.docker.slirp.exe: hvsock connected successfully
[15:31:40.686][ApiProxy ][Info ] Cancel connection...

Forgot to mention that I am able to pull the same images from the same registry on a Ubuntu VM on the same machine.

docker run --rm -v c:/Users/michael:/data alpine ls -la /data

Expected behavior

List of C:\Users\michael

Actual behavior

Only showing "." and "..".

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.

F72D0B33-B1B3-4168-B9E8-D812A10C0166/2016-08-21_00-03-22

Docker version is:

Client:
Version: 1.12.1-rc1
API version: 1.24
Go version: go1.6.3
Git commit: 7889dc7
Built: Fri Aug 12 18:35:53 2016
OS/Arch: windows/amd64
Experimental: true

Server:
Version: 1.12.1-rc1
API version: 1.24
Go version: go1.6.3
Git commit: 7889dc7
Built: Fri Aug 12 18:35:53 2016
OS/Arch: linux/amd64
Experimental: true

(switched to Beta, since this didn't work in stable 1.12)

• host distribution and version (Windows version, build number, etc)

Confirm that C: is shared. And user SCOTT-TIGER-MW\michael has full control.

Password of "michael" is very short and has no special characters.

Observation:
System reacts to C:/Users/not-found just as it reacts to C:/Users/michael ... It can't see anything in the share.

Tried to use share as "net use X: \SCOTT-TIGER-MW\michael\C"; dir X:\Users\michael. This worked as expected (list of content displayed).

Steps to reproduce the behavior

1. docker run --rm -v c:/Users/michael:/data alpine ls -la /data

I have tried entering credentials in settings with and without machine-name. Docker seems to be using the machine-name just fine. But none of the options work.

Expected behavior

Using the latest version of the Docker beta the following command should start a container and mount a directory with some files to a folder in the container:
docker run -it -v terraform/opt busybox
The files that are located in the terraform-folder on the host machine should also be located in the /opt-folder in the container.

Actual behavior

There are no files in the shared folder when the container is started.

Information

• Diagnostic ID: E311E898-0E69-43ED-B7C2-D7D932BFC458
• OS: Windows 10 pro, id 1607, build 14393
• Docker info: I have shared the relevant drive in the Docker for Windows GUI. I have tried to remove the shared drive with net share C /delete and share it again to no avail.

Steps to reproduce the behavior

1. Install the latest version of the Docker beta on latest version of Windows 10
2. Open a terminal
3. Run the following command: docker run -it -v terraform:/opt busybox
4. Go to the shared folder and check for contents

Expected behavior

Docker should start

Actual behavior

Docker fails to start and an Error reported in a window

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)

Steps to reproduce the behavior

Windows 10 pre and post Windows 10 anniverssary editions latest builds

1. installer Docker (also tried Beta version)
2. After installation completes the Docker is supposed to auto launch, but it fails to start

A diagnostic was uploaded with id: 5829B164-D591-4EF5-9283-A838DDE27F7D/2016-08-05_19-06-39

I've just started with Docker for Windows 10. Went through some getting started examples yesterday fine. Today, after updating to the latest stable release, I'm getting "The parameter is incorrect" coming up when I try to run containers. They run OK and can be seen with the ps command but they are not interactive.

Here is a simple example:

PS > docker run -it ubuntu bash
The parameter is incorrect.

PS > docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
6541c014737d        ubuntu              "bash"              11 seconds ago      Up 10 seconds                           adoring_hamilton

PS >

I only get the error when the -i flag is present.

My version info is as follows:

Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      linux/amd64

My diagnostic id is:
C8BAF08A-4F77-40FD-A92B-420733400683/2016-07-29_16-27-40

I am running Win10Pro with 16G with i7-3770K CPU 3.50GHz.

Just curious... Normally Docker fires up with 2 CPUs and 2048 MB.

Other than trial and error, are there any thoughts as to determining how to set these values?

Thank You

Expected behavior

Docker for windows startup normally

Actual behavior

the try icon keeps saying "Docker is starting...".

Errors in the log includes
[12:57:34.985][DataKit ][Info ] +1993786us fs9p [ERROR] dispatcher caught Unix.Unix_error(Unix.EPIPE, "bytes_read", ""): no more requests will be handled
[12:57:47.562][VpnKit ][Error ] com.docker.slirp.exe: Error reading /etc/resolv.conf: reading /etc/resolv.conf: Uwt.Uwt_error(Uwt.ENOENT, "uv_fs_open", "/etc/resolv.conf")

and it seems taking too long in this step:
[12:57:51.889][ApiProxy ][Info ] Dial Hyper-V socket a35d2eb3-5dbe-4c92-90e5-91d612a777eb:23a432c2-537a-4291-bcb5-d62504644739

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  F9A9FED6-041F-40EF-A2AD-5D2EA52437A8/2016-07-31_13-01-09
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)
  Windows 10 Pro 10.0.10586
  Docker version : 1.12.0-beta21 build 5671
  (also tried the non-beta released version, the same phenomenon)

Steps to reproduce the behavior

1. finish installation;
2. start docker

• Diagnostic ID from "Diagnose & Feedback" in the menu.
  B09AF01B-E38D-4EF5-8248-2BBFFC3539E4/2016-08-10_15-08-45
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)

This problem is reproductible; logs tell :
Failed to set up server socket listening on "hyperv-connect://72807d72-f692-4a03-a430-c76fb90ba0cd": Unix.Unix_error(Unix.ENETDOWN, "socket", "")

Windows 10 Pro Version 1511(version du systeme d'exploitation 10586.494) 3.5 Gbyte RAM, 2 cpu, Vt-x/Amd-V Active, service HyperV running

Context:
This Windows 10 Pro is installed in a VirtualBox hypervisor (5.0.24 r108.355) which is running on a Windows 7 (version 6.1 number 7601 service pack 1)

Steps to reproduce the behavior

1. ...Use a Windows 7 64 bits running in a physical machine
2. ... Install Virtual Box in this physical win 7
   3.. Install a Windows 10 pro (which will be virtual) in this Virtual Box
   4 .. Install docker for Windows in this Windows 10 Pro Virtual machine

FX Theodule

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\bagratte> dir stitch


    Directory: C:\Users\bagratte\stitch


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----         8/5/2016   1:04 PM              0 lilo.txt
-a----         8/5/2016   1:04 PM              0 mushu.txt


PS C:\Users\bagratte> docker run --rm -v c:/Users/bagratte/stitch:/data alpine ls -la /data
total 4
drwxr-xr-x    2 root     root            40 Aug  5 09:05 .
drwxr-xr-x   25 root     root          4096 Aug  5 09:05 ..
PS C:\Users\bagratte>

7DF51AAC-D04D-4FDC-AE2F-D19EAA0DC8EF/2016-08-05_13-06-39

Expected behavior

Upgrade and start.
Or provide a better message in case of issue.

Actual behavior

First, I tried the auto update which failed without any message (docker didn't start or started with the previous version).
Then, I tried a manual update which worked well but at the start I received:

Unable to start: The VM couldn't get an IP address after 60 tries
à Fatal, <Aucun fichier> : ligne 313
à Start-MobyLinuxVM, <Aucun fichier> : ligne 233
à <ScriptBlock>, <Aucun fichier> : ligne 322
   à Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
   à Docker.Backend.LinuxContainersEngine.DoStart(Settings settings)
   à Docker.Backend.LinuxContainersEngine.Start(Settings settings)
   à Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass7_0.<Register>b__0(Object[] parameters)
   à Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Information

• Diagnostic ID: 63FC49AC-136A-4694-8FC1-E651A239AEE3/2016-08-18_09-42-11
• host distribution: Windows 10.0.14393

Steps to reproduce the behavior

1. Upgrade to beta23
2. Try to start

Fix:
I had 127.0.0.1 docker.local in my hosts file to solve a previous issue. When I remove it, docker is running well.