如何在Visual Studio 2022中构建ARM32(armv7l)的ASP.NET Core Web App Docker镜像？

环境与需求 #

• Windows 10 + Visual Studio 2022
• 目标：构建ASP.NET Core 7.0 Web App的ARM32v7（armv7l）Docker镜像，打包为tar后部署到ARM设备
• 本地使用x64架构的.NET镜像时，可正常构建并启动容器，但切换到ARM32v7镜像时构建失败

报错信息 #

报错类型1：空引用异常+QEMU终止 #

error CTC1014: #12 [build 4/7] RUN dotnet restore "MyPlcDockerWebApp/MyPlcDockerWebApp.csproj"
 : error CTC1014: #12 sha256:353b0e08e28a4e967ad5c810f36eb6453202088e54405c3c2fb3cb70be70d3bf
 : error CTC1014: #12 9.885 Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.
 : error CTC1014: #12 9.888    at Regex1_Scan(RegexRunner, ReadOnlySpan`1)
 : error CTC1014: #12 9.888    at System.Text.RegularExpressions.Regex.RunAllMatchesWithCallback[TState](String inputString, ReadOnlySpan`1 inputSpan, Int32 startat, TState& state, MatchCallback`1 callback, RegexRunnerMode mode, Boolean reuseMatchObject)
 : error CTC1014: #12 9.893 qemu: uncaught target signal 6 (Aborted) - core dumped
 : error CTC1014: #12 9.921 Aborted
 : error CTC1014: #12 ERROR: executor failed running [/bin/sh -c dotnet restore "MyPlcDockerWebApp/MyPlcDockerWebApp.csproj"]: exit code: 134
 : error CTC1014: ------
 : error CTC1014:  > [build 4/7] RUN dotnet restore "MyPlcDockerWebApp/MyPlcDockerWebApp.csproj":
 : error CTC1014: ------
 : error CTC1014: executor failed running [/bin/sh -c dotnet restore "MyPlcDockerWebApp/MyPlcDockerWebApp.csproj"]: exit code: 134

报错类型2：QEMU段错误 #

error CTC1014: #12 [build 4/7] RUN dotnet restore "MyPlcDockerWebApp/MyPlcDockerWebApp.csproj"
 : error CTC1014: #12 sha256:7b86b8130fe749ac2390d652e6070685f81fc5ba8e51ca7d8fdf198580978932
 : error CTC1014: #12 5.024 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
 : error CTC1014: #12 5.044 Segmentation fault
 : error CTC1014: #12 ERROR: executor failed running [/bin/sh -c dotnet restore "MyPlcDockerWebApp/MyPlcDockerWebApp.csproj"]: exit code: 139
 : error CTC1014: ------

当前使用的Dockerfile #

#See https://aka.ms/customizecontainer to learn how to customize your debug container and how Visual Studio uses this Dockerfile to build your images for faster debugging.

FROM mcr.microsoft.com/dotnet/aspnet:7.0.4-jammy-arm32v7 AS base
WORKDIR /app
EXPOSE 80
EXPOSE 443

FROM mcr.microsoft.com/dotnet/sdk:7.0.202-jammy-arm32v7 AS build
WORKDIR /src
COPY ["MyPlcDockerWebApp/MyPlcDockerWebApp.csproj", "MyPlcDockerWebApp/"]
RUN dotnet restore "MyPlcDockerWebApp/MyPlcDockerWebApp.csproj"
COPY . .
WORKDIR "/src/MyPlcDockerWebApp"
RUN dotnet build "MyPlcDockerWebApp.csproj" -c Release -o /app/build

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

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

问题分析与解决方法 #

核心原因 #

这是QEMU模拟ARM32架构时的兼容性问题：Windows上的Docker Desktop通过QEMU模拟非本机架构（x64→ARM32），而.NET 7部分版本在QEMU模拟的ARM32环境下运行dotnet restore时，会触发正则表达式引擎的空引用或段错误。

解决方案 #

1. 改用交叉编译（推荐）
   在Windows主机的x64 SDK镜像中直接交叉编译ARM32应用，避免在QEMU里运行.NET SDK。修改后的Dockerfile如下：

   # 阶段1：x64 SDK中交叉编译ARM32应用
   FROM mcr.microsoft.com/dotnet/sdk:7.0 AS build
   WORKDIR /src
   COPY ["MyPlcDockerWebApp/MyPlcDockerWebApp.csproj", "MyPlcDockerWebApp/"]
   RUN dotnet restore "MyPlcDockerWebApp/MyPlcDockerWebApp.csproj" -r linux-arm
   COPY . .
   WORKDIR "/src/MyPlcDockerWebApp"
   RUN dotnet build "MyPlcDockerWebApp.csproj" -c Release -o /app/build -r linux-arm --no-restore
   
   FROM build AS publish
   RUN dotnet publish "MyPlcDockerWebApp.csproj" -c Release -o /app/publish -r linux-arm --no-restore /p:UseAppHost=false
   
   # 阶段2：使用ARM32运行时镜像
   FROM mcr.microsoft.com/dotnet/aspnet:7.0.4-jammy-arm32v7 AS final
   WORKDIR /app
   COPY --from=publish /app/publish .
   ENTRYPOINT ["dotnet", "MyPlcDockerWebApp.dll"]
   

   关键改动：在dotnet restore、build、publish命令中添加-r linux-arm参数，指定针对ARM32架构交叉编译，全程在x64环境执行，无需QEMU模拟。

2. 升级组件版本

   • 升级Docker Desktop到最新版本（自带更新的QEMU，修复部分模拟兼容性问题）
   • 更换为.NET 7的更高补丁版本镜像（如7.0.15-jammy-arm32v7），新版本可能修复了ARM32模拟环境下的正则引擎bug

3. 直接在ARM设备上构建
   将代码同步到目标ARM设备，直接在ARM设备上运行Docker构建，彻底避免QEMU模拟带来的兼容性问题

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