hi - I'm using Rancher Desktop on windows (1.4.1) and am having weird problems with docker build. It can find google.com from within the container but not api.nuget.org. The ping works fine from the host OS.

FROM <http://mcr.microsoft.com/dotnet/sdk:6.0-alpine|mcr.microsoft.com/dotnet/sdk:6.0-alpine>
#RUN ping <http://google.com|google.com>
RUN ping <http://api.nuget.org|api.nuget.org>

and the output

C:\temp\docker>docker build .
Sending build context to Docker daemon  2.048kB
Step 1/4 : FROM <http://mcr.microsoft.com/dotnet/sdk:6.0-alpine|mcr.microsoft.com/dotnet/sdk:6.0-alpine>
 ---> 68f959202edb
Step 2/4 : RUN ping <http://api.nuget.org|api.nuget.org>
 ---> Running in 190474634dc2
ping: bad address '<http://api.nuget.org|api.nuget.org>'
The command '/bin/sh -c ping <http://api.nuget.org|api.nuget.org>' returned a non-zero code: 1

A curl in the docker build returns this:

% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Could not resolve host: <http://api.nuget.org|api.nuget.org>
* Closing connection 0
curl: (6) Could not resolve host: <http://api.nuget.org|api.nuget.org>

Really not sure what is going on as other addresses appear to work fine so it shouldn't be a networking issue, but everything suggests it is

would suggest looking into Experimental Host Resolver setting in your settings.json file

I've seen similar issues in the past when the host machine/image has outdated root CAs, especially those prior to what I think was the letsencrypt older root ca expiration

@witty-honey-18052 @big-sugar-91946 Thanks. The Lima patch fixes the issue

Awesome!