docker build exception: Invoke-WebRequest : The remote name could not be resolved #6453

kkbruce · 2020-04-26T10:24:28Z

I have tried with the latest version of my channel (Stable)
I have uploaded Diagnostics
Diagnostics ID: 99736AF1-D022-4508-AE58-2007E0B76A8F/20200426101030

Expected behavior

download file in docker build with Windows container.

Actual behavior

Can't download the file in docker build with Windows container.

Invoke-WebRequest : The remote name could not be resolved: 'nginx.org'
At line:1 char:76
+ ... yContinue'; Invoke-WebRequest -Uri http://nginx.org/download/nginx-1. ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:Htt
   pWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShe
   ll.Commands.InvokeWebRequestCommand

Information

Windows Version:

c:\>ver

Microsoft Windows [版本 10.0.18363.815]

Docker Desktop Version:

docker version
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:23:10 2020
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.24)
  Go version:       go1.12.17
  Git commit:       afacb8b
  Built:            Wed Mar 11 01:37:20 2020
  OS/Arch:          windows/amd64
  Experimental:     false

Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Steps to reproduce the behavior

Dockerfile

# escape=`

FROM mcr.microsoft.com/windows/servercore:1909
LABEL maintainer="kkbruce" version="1.18.0"

SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]

# .zip file URL from http://nginx.org/en/download.html
RUN Invoke-WebRequest -Uri http://nginx.org/download/nginx-1.18.0.zip -OutFile nginx.zip ; `
	Expand-Archive nginx.zip -DestinationPath $Env:ProgramFiles ; `
	Remove-Item -Force nginx.zip ; `
	Move-Item $Env:ProgramFiles\nginx-* $Env:ProgramFiles\nginx

Run docker build -t kkbruce/nginx:1.18.0-servercore-1909 . and get Invoke-WebRequest : The remote name could not be resolved: 'nginx.org' exception.

I found a like issue pulla2908/docker-mssql-server-windows-developer-fti#2 , if I add --network "Default Switch" then docker build will success.

Now that the container wants to connect to the external network, do we need additional parameters?

Added: If after a while in Windows 10, it will return to an abnormal state.

The text was updated successfully, but these errors were encountered:

jeff994 · 2020-06-29T05:51:41Z

Same issues here

andyfisher100 · 2020-08-13T09:19:32Z

I also have a similar issue but when installing or using chocolatey package manager. It always seems to be when using powershell based commands.

If you take the following dockerfile as an example:

FROM mcr.microsoft.com/windows:1809
ADD https://aka.ms/vs/16/release/vs_enterprise.exe C:\\tools\\vs_enterprise19.exe
RUN powershell -NoProfile -ExecutionPolicy Bypass -Command "[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))"

The Visual Studio exe download will succeed but then the choco install script running from powershell will fail saying that the host cannot be resolved, like there is a dns/internet issue. However if there was an internet/dns issue, how did the VS exe download first?

uaonline · 2020-09-28T13:31:19Z

Similar issue being encountered with Docker Engine v19.03.11, on Windows Server 2016 host.

This isn't woking:
FROM mcr.microsoft.com/windows/servercore:ltsc2016
RUN Invoke-WebRequest -UseBasicParsing "http://nodejs.org/dist/v12.18.3/node-v12.18.3-win-x64.zip" -OutFile C:\nodejs.zip

Yet this works:
FROM mcr.microsoft.com/windows/servercore:ltsc2016
ADD http://nodejs.org/dist/v12.18.3/node-v12.18.3-win-x64.zip C:\nodejs.zip

docker-robott · 2020-12-27T01:00:09Z

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

RichardMM · 2021-01-01T13:19:27Z

/remove-lifecycle stale

RichardMM · 2021-01-01T13:19:49Z

I am experiencing the same issue as well

RichardMM · 2021-01-01T13:21:11Z

@kkbruce hello,
Were you able to get the reason for this or a fix because the ADD function does not work in all scenarios

kkbruce · 2021-01-06T16:11:41Z

@RichardMM
In the new version of Docker Desktop, I did not repeat this problem again. Otherwise, you can try the --network "Default Switch" parameter.

shanz1999 · 2021-01-14T09:28:08Z

Same problem here following https://www.aeons.dev/2020/02/19/win2016-with-vsbuild-docker/

Fix DNS issue in Windows Container by adding the following --network switch: --network "Default Switch" docker/for-win#6453 (comment) docker build --network "Default Switch" -t willh/mssql-server-windows-developer:20H2 .

docker-robott · 2021-04-14T01:00:18Z

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

darkvertex · 2021-04-14T21:00:17Z

/remove-lifecycle stale

phmonte · 2021-04-15T00:45:39Z

Same problem in docker build and docker run, works only with --network "Default Switch" parameter.

docker-robott · 2021-07-14T01:00:16Z

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

Cpt-Falcon · 2021-07-19T20:32:16Z

/remove-lifecycle stale

Cpt-Falcon · 2021-07-19T20:32:32Z

This problem still exists and is quite problematic

hatasaki · 2021-09-23T06:15:45Z

Hi all,
I faced same issue then I solved it based on the info written in this post.
I hope it can help you.

This often happens when there are multiple networking adapters (Ethernet, Wi-Fi, etc.) present on the host. The priority of these adapters needs to be configured properly in order for the Windows networking stack to correctly choose gateway routes. You can fix this by setting your primary internet-connected networking adapter to have the lowest InterfaceMetric value. Try these Powershell commands from an elevated console:

Get-NetIPInterface -AddressFamily IPv4 | Sort-Object -Property InterfaceMetric -Descending

Again, you want your host's primary internet-connected network adapter to have the lowest InterfaceMetric value.

Use this command to make the change (example assumes primary adapter InterfaceAlias is 'Wi-Fi'):

Set-NetIPInterface -InterfaceAlias 'Wi-Fi' -InterfaceMetric 3

That should do it. If your host's primary network adapter is bridged because you have an External virtual switch setup in Hyper-V, then you will set the external virtual switch to have the lowest InterfaceMetric value.

You can verify your routing tables by using this command (the last line should show the primary adapter's gateway address along with it's ifMetric value):

Get-NetRoute -AddressFamily IPv4

I hope this helps!

klawingco · 2021-10-01T05:30:42Z

I wasted 2 hours of time trying to fix this. What I've done is removing my wifi dongle (I am connected to ethernet via wired LAN). I believe if it's built-in. Disabling it will suffice.
Othersie If you are working on a laptop with multiple network adapters @hatasaki comment might help.

DatKyle · 2021-10-04T08:06:07Z

@hatasaki's comment helped fix this for me. One thing to note is I had 2 interfaces (Network 8 and 9) with metrics 1, when I updated the required interface (network 3) to metrics 1, it still didn't work. I had to update the Network 8 and 9 metrics to be 2 to get docker to use the correct interface.

Cpt-Falcon · 2021-10-29T14:13:15Z

All, WSL 1 was working fine but WSL2 does not work at all. Something is clearly wrong. However, I was able to get around everything and work locally OR on a VPN with the following extremely helpful github repo:

https://github.com/sakai135/wsl-vpnkit

Install the following and your problems should be solved.

selek55 · 2021-12-14T20:45:18Z

/remove-lifecycle stale

docker-robott · 2022-03-14T01:00:19Z

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

mulder999 · 2022-03-30T08:11:24Z

/remove-lifecycle stale

docker-robott · 2022-06-28T01:00:10Z

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

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

francsiswanto · 2022-08-15T04:18:30Z

In my case, I just do these:

remove all containers
prune docker network
done

It's work for me.

docker-robott · 2022-09-14T03:00:10Z

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

docker-robott added the lifecycle/stale label Dec 27, 2020

docker-robott removed the lifecycle/stale label Jan 1, 2021

hmccoll mentioned this issue Feb 11, 2021

docker build exception: Invoke-WebRequest : The remote name could not be resolved jadesoftwarenz/JADE-container-examples#1

Open

doggy8088 mentioned this issue Apr 13, 2021

Cannot resolve host name in Docker Desktop Windows #3810

Closed

2 tasks

docker-robott added the lifecycle/stale label Apr 14, 2021

docker-robott removed the lifecycle/stale label Apr 14, 2021

docker-robott added the lifecycle/stale label Jul 14, 2021

docker-robott removed the lifecycle/stale label Jul 19, 2021

docker-robott added the lifecycle/stale label Mar 14, 2022

docker-robott removed the lifecycle/stale label Mar 30, 2022

docker-robott added the lifecycle/stale label Jun 28, 2022

docker-robott closed this as completed Jul 28, 2022

docker locked and limited conversation to collaborators Sep 14, 2022

docker-robott added the lifecycle/locked label Sep 14, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docker build exception: Invoke-WebRequest : The remote name could not be resolved #6453

docker build exception: Invoke-WebRequest : The remote name could not be resolved #6453

kkbruce commented Apr 26, 2020 •

edited

Loading

jeff994 commented Jun 29, 2020

andyfisher100 commented Aug 13, 2020

uaonline commented Sep 28, 2020 •

edited

Loading

docker-robott commented Dec 27, 2020

RichardMM commented Jan 1, 2021

RichardMM commented Jan 1, 2021

RichardMM commented Jan 1, 2021

kkbruce commented Jan 6, 2021

shanz1999 commented Jan 14, 2021

docker-robott commented Apr 14, 2021

darkvertex commented Apr 14, 2021

phmonte commented Apr 15, 2021

docker-robott commented Jul 14, 2021

Cpt-Falcon commented Jul 19, 2021

Cpt-Falcon commented Jul 19, 2021

hatasaki commented Sep 23, 2021

klawingco commented Oct 1, 2021 •

edited

Loading

DatKyle commented Oct 4, 2021

Cpt-Falcon commented Oct 29, 2021 •

edited

Loading

selek55 commented Dec 14, 2021

docker-robott commented Mar 14, 2022

mulder999 commented Mar 30, 2022

docker-robott commented Jun 28, 2022

francsiswanto commented Aug 15, 2022

docker-robott commented Sep 14, 2022

docker build exception: Invoke-WebRequest : The remote name could not be resolved #6453

docker build exception: Invoke-WebRequest : The remote name could not be resolved #6453

Comments

kkbruce commented Apr 26, 2020 • edited Loading

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

jeff994 commented Jun 29, 2020

andyfisher100 commented Aug 13, 2020

uaonline commented Sep 28, 2020 • edited Loading

docker-robott commented Dec 27, 2020

RichardMM commented Jan 1, 2021

RichardMM commented Jan 1, 2021

RichardMM commented Jan 1, 2021

kkbruce commented Jan 6, 2021

shanz1999 commented Jan 14, 2021

docker-robott commented Apr 14, 2021

darkvertex commented Apr 14, 2021

phmonte commented Apr 15, 2021

docker-robott commented Jul 14, 2021

Cpt-Falcon commented Jul 19, 2021

Cpt-Falcon commented Jul 19, 2021

hatasaki commented Sep 23, 2021

klawingco commented Oct 1, 2021 • edited Loading

DatKyle commented Oct 4, 2021

Cpt-Falcon commented Oct 29, 2021 • edited Loading

selek55 commented Dec 14, 2021

docker-robott commented Mar 14, 2022

mulder999 commented Mar 30, 2022

docker-robott commented Jun 28, 2022

francsiswanto commented Aug 15, 2022

docker-robott commented Sep 14, 2022

kkbruce commented Apr 26, 2020 •

edited

Loading

uaonline commented Sep 28, 2020 •

edited

Loading

klawingco commented Oct 1, 2021 •

edited

Loading

Cpt-Falcon commented Oct 29, 2021 •

edited

Loading