Timeout when trying to login to internal registry

[ghost]

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

[friism]

Hm, is your host using a proxy?

[ghost]

The host uses a proxy and I configured Docker to use it.
[Edit] Sorry I made a confusion with another issue about a certificate error. I tried with and without the proxy configuration, but I want to make other tests. I come back with the results later

[ghost]

After some more tests, I got the following results:

• If the internal docker registry host is added on the exclusion list of the proxy, I get the timeout error:
  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
• If the internal docker registry host is not added on the exclusion list of the proxy, I get the following error:
  Error response from daemon: Get et https://docker-rep.dep.ca.inet:18443/v1/users/: Tunnel or SSL Forbidden

[bbodenmiller]

Based on #36, looks like you must mark your registry as insecure but it does look like you have other problems as well.

[dgageot]

Hi @oscarpicasso-intact, could you please test Beta25? It contains fixes to the networking and dns resolution so maybe it can help.

[dgageot]

Hi @oscarpicasso-intact, I'll be closing this issue in a couple of days under the assumption that more recent betas have fixed the issue for you. Thanks a lot for your contribution and please feel free to reopen the ticket with more information to help us reproduce and fix!

[rn]

closing as per @dgageot comment 12 days ago

[M3ssman]

Hello,
I'm having the same Issues right now when I try to "docker login" from a Windows 10 Host using Docker Toolbox with a SSH Tunnel to an Ubuntu Docker-Daemon.

Error response from daemon: Get https://nexus.intra.teleport.de:9093/v1/users/: dial tcp <server-ip>:9093: i/o timeout

It fails also from the Windows-Subsystem 4 Linux, i.e. after installing a separate Docker-Client (docker-17.03, Ubuntu 16.04) in this intergrated Bash-System.
Please note, it worked from within a Ubuntu 16.04 VM using VirtualBox (running on the same Windows 10 Host). Looks like Windows has a Problem with the SSH-Tunnel?

[malcolmm83]

having the same issue. I'm running version 18.05.0-ce-rc1-win63 edge .
Could my VPN be causing a problem? I was able to get this to work with minikube (vbox) .

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked