Replies: 2 comments 1 reply
-
|
The same commands with network mode host:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I can't reproduce this on macOS 26 using Docker Desktop or Windows 11 using Docker Destop. It looks like you're using Docker inside WSL on Ubuntu 24.04. Perhaps somtehing weird is happening with the WSL networking? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
Using
mcr.microsoft.com/dotnet/sdk:8.0the dotnet tool install and direct HttpClient calls tohttps://api.nuget.org/v3/index.jsoninside a container on Docker network mode bridge consistently time out. The same calls succeed when the container uses--network host. Directcurlrequests inside the same container (bridge) also succeed, so this appears specific to the dotnet HTTP stack or NuGet client behavior inside Docker bridge networking rather than general network connectivity.Which .NET image(s) are you using?
mcr.microsoft.com/dotnet/sdk:8.0
Steps to reproduce
Using the SDK image, attempt to install a dotnet tool:
Result:
TIMEOUT.Expected result:
dotnet tool install -g dotnet-gcdumpshould complete successfully and finish downloading packages from https://api.nuget.org/v3/index.json within a normal timeframe.Minimal HttpClient repro:
Result: EX after 30.03s: The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing.
curlfrom the same container (bridge) works:Result: the expected json within 0.117710s
Other information
The full output of
dotnet tool installafter removing thetimeout 30command:Output of
docker versionOutput of
docker infoBeta Was this translation helpful? Give feedback.
All reactions