ASP.NET Core 8.0 Docker容器中HTTP请求超时问题求助

核心现象 #

• 在Ubuntu 22.04服务器的Docker容器中运行ASP.NET Core 8.0应用时，发起POST/GET请求、调用MailKit的SendAsync发送邮件、通过IHttpClientFactory/HttpClient发起请求，均出现504超时异常，无法接收远程响应。
• 本地Windows环境运行该应用可正常发送请求并接收响应。
• 服务器宿主机命令行用curl请求目标地址可得到200响应。
• 容器内尝试安装curl时无法下载资源（网络不通）。
• 此前另一容器出现过相同问题，通过在docker-compose中设置network_mode: host解决，但本次调整DNS配置后无效。
• 同一服务器上运行的Seq日志容器无此网络问题，仅ASP.NET Core容器受影响。

配置文件 #

Dockerfile #

FROM mcr.microsoft.com/dotnet/aspnet:8.0 AS base
#USER app
WORKDIR /app
EXPOSE 8080
EXPOSE 8081

FROM mcr.microsoft.com/dotnet/sdk:8.0 AS build
ARG BUILD_CONFIGURATION=Release
WORKDIR /src
COPY ["SwishLeadplace/SwishLeadplace.csproj", "SwishLeadplace/"]
COPY ["SwishLeadplace.BusinessLogic/ClassLibrary1/BusinessLogic.csproj", "SwishLeadplace.BusinessLogic/ClassLibrary1/"]
COPY ["SwishLeadplace.BusinessLogic.Core/BusinessLogic.Core/BusinessLogic.Core.csproj", "SwishLeadplace.BusinessLogic.Core/BusinessLogic.Core/"]
COPY ["SwishLeadplace.DataAccess/SwishLeadplace.DataAccess/SwishLeadplace.DataAccess.csproj", "SwishLeadplace.DataAccess/SwishLeadplace.DataAccess/"]
COPY ["SwishLeadplace.Shared/SwishLeadplace.Shared/SwishLeadplace.Shared.csproj", "SwishLeadplace.Shared/SwishLeadplace.Shared/"]
RUN dotnet restore "./SwishLeadplace/SwishLeadplace.csproj"
COPY . .
WORKDIR "/src/SwishLeadplace"
RUN dotnet build "./SwishLeadplace.csproj" -c $BUILD_CONFIGURATION -o /app/build

FROM build AS publish
ARG BUILD_CONFIGURATION=Release
RUN dotnet publish "./SwishLeadplace.csproj" -c $BUILD_CONFIGURATION -o /app/publish /p:UseAppHost=false

FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "SwishLeadplace.dll"]

docker-compose.yml #

services:
  leadplace_service:
    image: leadplace_service:latest
    build:
      context: .
      dockerfile: Dockerfile
    restart: always
    ports:
      - "3333:8080"
      - "3332:8081"
    environment:
      ASPNETCORE_ENVIRONMENT: "Development"
      ASPNETCORE_URLS: "http://+:8080"

排查与解决方案建议 #

1. 验证容器网络基础连通性 #

进入容器执行以下命令排查网络层级问题：

# 进入容器
docker exec -it <容器ID> /bin/bash
# 测试IP连通性
ping 8.8.8.8
# 测试域名解析
nslookup google.com

• 如果ping不通IP：说明容器网络路由存在故障，需检查Docker网桥配置或宿主机防火墙规则。
• 如果nslookup失败：说明DNS解析异常，可在docker-compose.yml中手动指定DNS服务器：

  services:
    leadplace_service:
      # 其他配置不变
      dns:
        - 8.8.8.8
        - 1.1.1.1
  

2. 检查宿主机防火墙规则 #

Ubuntu宿主机的ufw防火墙可能限制了容器的出站流量，执行以下命令验证并调整：

# 查看防火墙状态
sudo ufw status
# 允许Docker默认网桥（docker0）的出站流量
sudo ufw allow out on docker0

3. 再次测试host网络模式 #

虽然此前配置DNS无效，但可再次尝试启用network_mode: host验证是否为Docker网桥的问题：

services:
  leadplace_service:
    # 其他配置不变
    network_mode: host
    environment:
      ASPNETCORE_ENVIRONMENT: "Development"
      ASPNETCORE_URLS: "http://+:3333" # 需调整端口避免与宿主机冲突

4. 排查应用代理配置 #

如果服务器环境使用了代理服务器，需在ASP.NET Core应用中配置代理：

• 在appsettings.json中添加代理配置：

  "HttpClient": {
    "Proxy": {
      "Address": "http://代理服务器地址:端口",
      "BypassOnLocal": true
    }
  }
  

• 或者在代码中手动配置HttpClientHandler：

  var handler = new HttpClientHandler
  {
      Proxy = new WebProxy("http://代理服务器地址:端口"),
      UseProxy = true
  };
  var httpClient = new HttpClient(handler);
  

5. 替换基础镜像测试 #

尝试更换基础镜像，排查是否为官方ASP.NET镜像的网络配置问题：

# 临时替换为Ubuntu基础镜像
FROM ubuntu:22.04 AS base
RUN apt-get update && apt-get install -y dotnet-runtime-8.0
WORKDIR /app
EXPOSE 8080
EXPOSE 8081

# 后续build、publish步骤保持不变

内容的提问来源于stack exchange，提问作者Mark