17

I am trying to build an image using docker windows container. Here is my dockerfile

FROM mcr.microsoft.com/windows/servercore:ltsc2019 as installer
RUN Invoke-WebRequest -URI 'www.google.com'

When I run this it is failing to connect to google.com

Invoke-WebRequest : The remote name could not be resolved: 'www.google.com'
At line:1 char:73

I am working on a corporate network and I tried setting proxy using RUN netsh winhttp set proxy proxy-server="http://proxy.com:80" bypass-list="*.xyz.com" and also imported the registry HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

ipconfig /all inside my container gives below result

Windows IP Configuration

   Host Name . . . . . . . . . . . . : 0d5119fe9ce4
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
   Physical Address. . . . . . . . . : 00-15-5D-B4-55-54
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fd80::a1f4:ab74:983:af83%4(Preferred)
   IPv4 Address. . . . . . . . . . . : 172.xxx.xxx.xx(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.xxx.xxx.xx
   Default Gateway . . . . . . . . . : 172.xxx.xxx.xx
   DHCPv6 IAID . . . . . . . . . . . : 67114333
   DHCPv6 Client DUID. . . . . . . . : 00-01-40-01-25-D1-CB-C4-00-15-5D-D4-A5-54
   DNS Servers . . . . . . . . . . . : 172.xxx.xxx.xx
                                       10.xxx.xxx.xx
   NetBIOS over Tcpip. . . . . . . . : Disabled

I suspect there is some dns/firewall issue or not setting proxy in a correct way. Can someone help me in identifying the root cause and fixing this issue.

Madan Sandiri
  • 400
  • 1
  • 3
  • 11
  • Do you get the same error when you create a container and attempt to connect to the internet? `docker run -it mcr.microsoft.com/windows/servercore:ltsc2019 powershell` then `Invoke-WebRequest -Uri 'www.google.com' -UseBasicParsing` inside the container? – Mike-314 Mar 02 '20 at 17:10

5 Answers5

31

I have had the same problem and was able to resolve it setting the DNS.

If you are making the call during build time you can set it in your docker daemon. In Docker Desktop go to "Settings" > "Docker Engine" and add the following to the JSON config:

"dns": ["1.1.1.1"]

https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-dns-options

If you are experiencing the problem during run time you can add the dns argument

--dns 1.1.1.1

https://docs.docker.com/engine/reference/run/#network-settings

flec
  • 2,891
  • 1
  • 22
  • 30
  • 1
    I am still shocked that this worked for me. Im on windows 11 docker-desktop and any internet build operation was totally flaky. changing the dns setting fixed the flaky inet operations – BozoJoe Dec 06 '22 at 15:17
  • OMG I tried everything this worked for me too! I have development DB in aws rds and need to develop locally with my container. This worked! I tried everything and couldn't connect but this did it! (I don't even know why it works lol) – EddieV223 May 14 '23 at 23:56
  • In my case, a simple day all my dockers lost his internet access without reason, this works, thanks – Daniel Restrepo Jun 10 '23 at 21:46
  • This should be on every MS page related to Docker & Windows Containers. 3 days of pi$$in' about trying to get the "Quickstart" app to run :-( – Ross Halliday Aug 16 '23 at 11:49
8

Specifying network command can be used as a workaround. Works for both build and run

docker build --network="Default Switch" .

docker run --rm -it --network="Default Switch" mcr.microsoft.com/windows/servercore:ltsc2019

And the name is the one from here:

docker network ls
NETWORK ID     NAME             DRIVER    SCOPE
79b90200b5ad   Default Switch   ics       local
07ffb031d4b7   nat              nat       local
6682d6220de5   none             null      local

For some reason docker default (nat) doesn't have internet connection.

lukee
  • 843
  • 9
  • 12
  • I got it fixed eventually so default (`nat`) started working, but don't remember exactly how. I think I had something misconfigured in my network card that it was using some weird Windows proxy. – lukee Mar 09 '23 at 14:50
4

Finally found a straightforward answer for this here https://github.com/docker/for-win/issues/2760#issuecomment-430889666

Basically need to set your internet connection as top priority:

  1. Find you internet interface e.g. 'Wi-Fi' Get-NetIPInterface -AddressFamily IPv4 | Sort-Object -Property InterfaceMetric -Descending

  2. Make it top priority by setting it to the lowest value Set-NetIPInterface -InterfaceAlias 'Wi-Fi' -InterfaceMetric 1

Co-der
  • 363
  • 1
  • 14
  • 1
    Another suggestion in the linked discussion was what did it for me: disabling the ethernet adapter. I'm on my laptop on wifi and Hyper-V was sharing the wrong network adapter with the underlying VM used by docker – Loris Jun 21 '23 at 16:15
3

I was struggling with a similar issue, and it was because I was connected to a VPN and hadn't enabled the setting "Allow local (LAN) access when using VPN (if configured)" in Cisco AnyConnect. Just in case anyone else is struggling with a similar issue.

IBN
  • 199
  • 1
  • 9
0

In Docker Desktop go to "Settings" > "Docker Engine" and add the below line to the

JSON config:
"dns":[8.8.8.8]
It looks like this:
{
  "dns": [
    "8.8.8.8"
  ],
  "experimental": false
}

Apply and Restart. Once restarted, go to any running container and do "ping google.com" it should work. Thanks

toyota Supra
  • 3,181
  • 4
  • 15
  • 19
Ranga Teja
  • 1
  • 1