.NET 8升级后容器启动停滞问题求助

将ASP.NET Core应用升级至.NET 8后，本地非容器环境运行正常，但Azure容器实例、本地Docker容器均无法完成启动，日志卡在**Refreshed catalog data**阶段后无任何后续输出。

相关文件 #

Dockerfile

FROM mcr.microsoft.com/dotnet/aspnet:8.0-bookworm-slim AS base
WORKDIR /app
EXPOSE 80
EXPOSE 443
COPY publish .
ENTRYPOINT ["./Application"]

Azure SCM日志片段

2023-12-05T14:45:05.036017766Z [14:45:04 Warning] Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository
2023-12-05T14:45:05.037320672Z Storing keys in a directory '/root/ASP.NET/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
2023-12-05T14:45:05.037338772Z 
2023-12-05T14:45:05.315275542Z [14:45:05 Warning] Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager
2023-12-05T14:45:05.315355042Z No XML encryptor configured. Key {a052ec83-e17e-4d70-8bcf-2537c7492700} may be persisted to storage in unencrypted form.
2023-12-05T14:45:05.315362542Z 
2023-12-05T14:45:05.382496649Z [14:45:05 Information] Application.Worker.CatalogChangedMessageProcessor
2023-12-05T14:45:05.382566849Z Refreshing catalog data
2023-12-05T14:45:05.382574549Z 
2023-12-05T14:45:08.077826368Z [14:45:08 Warning] Microsoft.EntityFrameworkCore.Model.Validation
2023-12-05T14:45:08.079457876Z The property 'OemCustomer.ClientApplicationIds' is a collection or enumeration type with a value converter but with no value comparer. Set a value comparer to ensure the collection/enumeration elements are compared correctly.
2023-12-05T14:45:08.079477476Z 
2023-12-05T14:45:14.160127997Z [14:45:14 Information] Application.Worker.CatalogChangedMessageProcessor
2023-12-05T14:45:14.160225699Z Refreshed catalog data
2023-12-05T14:45:14.160235499Z 

1. 定位卡住的核心逻辑 #

日志最后停在Refreshed catalog data，说明CatalogChangedMessageProcessor完成数据刷新后，应用后续初始化流程阻塞。重点检查：

• 数据刷新完成后的代码逻辑，是否存在线程阻塞、死锁（比如同步等待未就绪的资源）
• Worker服务的启动逻辑，是否在等待某个外部依赖（消息队列、第三方API）的响应

2. 排查容器环境配置差异 #

本地非容器正常、容器异常，优先排查环境变量与依赖连通性：

• 对比本地与容器的环境变量，确保数据库连接字符串、消息队列配置等完全一致
• 在Dockerfile中添加工具测试外部服务连通性：

  FROM mcr.microsoft.com/dotnet/aspnet:8.0-bookworm-slim AS base
  RUN apt-get update && apt-get install -y curl iputils-ping
  WORKDIR /app
  EXPOSE 80
  EXPOSE 443
  COPY publish .
  ENTRYPOINT ["./Application"]
  

  启动容器后手动执行curl/ping命令，验证容器是否能访问所有依赖服务。

3. 修复EF Core Value Comparer警告 #

.NET 8对EF Core验证更严格，虽警告本身不致命，但可能触发未预期行为。为OemCustomer.ClientApplicationIds配置Value Comparer：

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    modelBuilder.Entity<OemCustomer>()
        .Property(e => e.ClientApplicationIds)
        .HasConversion(
            v => string.Join(',', v),
            v => v.Split(',', StringSplitOptions.RemoveEmptyEntries).ToList())
        .Metadata.SetValueComparer(new ValueComparer<List<string>>(
            (c1, c2) => c1.SequenceEqual(c2),
            c => c.Aggregate(0, (a, v) => HashCode.Combine(a, v.GetHashCode())),
            c => c.ToList()));
}

4. 提升日志 Verbosity 获取更多细节 #

修改应用日志配置，输出更详细的启动过程：

• 在appsettings.json中调整日志等级：

  {
    "Logging": {
      "LogLevel": {
        "Default": "Debug",
        "Microsoft.AspNetCore": "Debug"
      }
    }
  }
  

• 或在容器启动时添加环境变量：ASPNETCORE_LOGGING__LOGLEVEL__DEFAULT=Debug

5. 验证发布包架构兼容性 #

确保publish目录下的文件是针对linux-x64架构发布的，避免跨架构兼容问题：
发布命令：

dotnet publish -c Release -r linux-x64 --self-contained false

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