.NET 5 Docker镜像中Playwright Chromium启动失败问题求助

• 核心触发点是代码配置了Headless = false：Docker容器默认无图形显示服务，Chromium非无头模式依赖X11图形环境，缺少该环境会直接导致浏览器启动崩溃。日志中出现的cpufreq相关报错仅为非致命警告，不是启动失败的原因。
• Dockerfile依赖安装逻辑错误：所有系统依赖都安装在build阶段，但最终运行镜像基于未装依赖的base runtime镜像，运行时缺少必要的系统组件。
• 缺少容器环境必备启动参数：Docker内运行Chromium必须添加--no-sandbox参数，否则会因权限不足启动失败。
• 浏览器路径不匹配：单独通过npm安装的playwright-chromium，.NET版Playwright无法自动识别正确的执行路径。

1. 修正Chromium启动配置 #

优先使用无头模式适配容器无图形环境，同时添加必要启动参数：

await using var browser = await playwright.Chromium.LaunchAsync(new BrowserTypeLaunchOptions 
            {
                Headless = true,
                Args = new[] { "--disable-dev-shm-usage", "--no-sandbox" }
            });

如果确实需要非无头模式运行，需要在启动容器时挂载宿主机X11显示套接字，执行命令参考：
docker run -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix <镜像名称>
该方案仅适用于宿主机为Linux桌面环境的场景，服务器环境不推荐使用。

2. 修正Dockerfile结构与依赖安装逻辑 #

使用Playwright官方自带的依赖安装命令，避免手动安装缺漏，同时调整阶段结构确保依赖打包到最终运行镜像：

FROM mcr.microsoft.com/dotnet/runtime:5.0-buster-slim AS base
WORKDIR /app
RUN apt-get update -yq && apt-get upgrade -yq && \
    apt-get install -yq --no-install-recommends ca-certificates curl && \
    rm -rf /var/lib/apt/lists/*

FROM mcr.microsoft.com/dotnet/sdk:5.0-buster-slim AS build
WORKDIR /src
COPY ["Agent.csproj", "Agent/"]
RUN dotnet restore "Agent/Agent.csproj"
COPY . "/src/Agent"
WORKDIR "/src/Agent"
RUN dotnet add package Microsoft.Playwright --version 1.15.2
RUN dotnet build "Agent.csproj" -c Release -o /app/build
# 安装对应版本Chromium
RUN ~/.nuget/packages/microsoft.playwright/1.15.2/tools/playwright.sh install chromium

FROM build AS publish
RUN dotnet publish "Agent.csproj" -c Release -o /app/publish
# 自动安装所有Chromium运行依赖
RUN ~/.nuget/packages/microsoft.playwright/1.15.2/tools/playwright.sh install-deps chromium

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

删除原Dockerfile中手动安装零散依赖、npm安装playwright-chromium的相关步骤，避免版本冲突。

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