Docker容器内Linux/amd64 Unity应用启动停滞求助

问题现象 #

我有一个Linux/amd64架构的Unity非编辑器无头应用，在Docker容器内运行时，输出到Unable to preload the following plugins: libsentry.so后就静默停滞，进程保持存活但无任何后续输出；但在容器外运行时，能正常完成引擎初始化并继续执行后续逻辑。

容器外正常运行日志 #

vik@r1g:/mnt/c/Users/vik/Downloads/test-server/server-headless-230620-1057$ ./server-headless-230620-1057
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"
Mono path[0] = '/mnt/c/Users/vik/Downloads/test-server/server-headless-230620-1057/server-headless-230620-1057_Data/Managed'
Mono config path = '/mnt/c/Users/vik/Downloads/test-server/server-headless-230620-1057/server-headless-230620-1057_Data/MonoBleedingEdge/etc'
Preloaded 'lib_burst_generated.so'
Preloaded 'libenet.so'
Initialize engine version: 2021.3.22f1 (b6c551784ba3)
[Subsystems] Discovering subsystems at path /mnt/c/Users/vik/Downloads/test-server/server-headless-230620-1057/server-headless-230620-1057_Data/UnitySubsystems
Forcing GfxDevice: Null
GfxDevice: creating device client; threaded=0; jobified=0
NullGfxDevice:
    Version:  NULL 1.0 [1.0]
    Renderer: Null Device
    Vendor:   Unity Technologies

and so on...

容器内停滞时的日志 #

2023-06-21 10:44:41 [UnityMemory] Configuration Parameters - Can be set up in boot.config
2023-06-21 10:44:41     "memorysetup-bucket-allocator-granularity=16"
2023-06-21 10:44:41     "memorysetup-bucket-allocator-bucket-count=8"
2023-06-21 10:44:41     "memorysetup-bucket-allocator-block-size=4194304"
2023-06-21 10:44:41     "memorysetup-bucket-allocator-block-count=1"
2023-06-21 10:44:41     "memorysetup-main-allocator-block-size=16777216"
2023-06-21 10:44:41     "memorysetup-thread-allocator-block-size=16777216"
2023-06-21 10:44:41     "memorysetup-gfx-main-allocator-block-size=16777216"
2023-06-21 10:44:41     "memorysetup-gfx-thread-allocator-block-size=16777216"
2023-06-21 10:44:41     "memorysetup-cache-allocator-block-size=4194304"
2023-06-21 10:44:41     "memorysetup-typetree-allocator-block-size=2097152"
2023-06-21 10:44:41     "memorysetup-profiler-bucket-allocator-granularity=16"
2023-06-21 10:44:41     "memorysetup-profiler-bucket-allocator-bucket-count=8"
2023-06-21 10:44:41     "memorysetup-profiler-bucket-allocator-block-size=4194304"
2023-06-21 10:44:41     "memorysetup-profiler-bucket-allocator-block-count=1"
2023-06-21 10:44:41     "memorysetup-profiler-allocator-block-size=16777216"
2023-06-21 10:44:41     "memorysetup-profiler-editor-allocator-block-size=1048576"
2023-06-21 10:44:41     "memorysetup-temp-allocator-size-main=4194304"
2023-06-21 10:44:41     "memorysetup-job-temp-allocator-block-size=2097152"
2023-06-21 10:44:41     "memorysetup-job-temp-allocator-block-size-background=1048576"
2023-06-21 10:44:41     "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
2023-06-21 10:44:41     "memorysetup-temp-allocator-size-background-worker=32768"
2023-06-21 10:44:41     "memorysetup-temp-allocator-size-job-worker=262144"
2023-06-21 10:44:41     "memorysetup-temp-allocator-size-preload-manager=262144"
2023-06-21 10:44:41     "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
2023-06-21 10:44:41     "memorysetup-temp-allocator-size-audio-worker=65536"
2023-06-21 10:44:41     "memorysetup-temp-allocator-size-cloud-worker=32768"
2023-06-21 10:44:41     "memorysetup-temp-allocator-size-gfx=262144"
2023-06-21 10:44:41 Mono path[0] = '/home/twindrums/server-headless-230425-0757/server-headless-230425-0757_Data/Managed'
2023-06-21 10:44:41 Mono config path = '/home/twindrums/server-headless-230425-0757/server-headless-230425-0757_Data/MonoBleedingEdge/etc'
2023-06-21 10:44:41 Preloaded 'lib_burst_generated.so'
2023-06-21 10:44:41 Preloaded 'libenet.so'
2023-06-21 10:44:41 Unable to preload the following plugins:
2023-06-21 10:44:41 libsentry.so

已尝试的解决方法 #

• 更换不同的Docker基础镜像（Debian、Ubuntu、稳定版、精简版等）
• 使用不同版本的Unity构建应用
• 将宿主机上运行中的应用文件手动移入容器（问题依旧）
• 移除应用中的所有额外包
• 使用Unity专用服务器构建选项，并添加-batchmode -nographics启动参数

可能的解决方案 #

1. 修复libsentry.so依赖缺失问题 #

容器内明确提示无法预加载libsentry.so，虽然宿主机运行时无此报错，但Unity引擎初始化阶段可能因依赖缺失进入无限等待而非直接崩溃。可以尝试：

• 从宿主机系统中找到libsentry.so文件，复制到容器内应用的Plugins目录，或系统库路径（如/usr/lib/x86_64-linux-gnu/）
• 在Dockerfile中安装sentry相关依赖包，例如基于Debian/Ubuntu的镜像执行：

  apt-get update && apt-get install -y libsentry-dev
  

  （注：实际包名需根据镜像版本确认，若找不到对应包，直接复制宿主机的库文件更稳妥）

2. 强化无头模式参数，强制禁用图形子系统 #

即使添加了-batchmode -nographics，Unity可能仍在尝试初始化某些图形相关组件，在Docker隔离环境中导致阻塞。可以添加更多启动参数：

./server-headless-230620-1057 -batchmode -nographics -logfile - -force-device-type Null -disable-gfx-jobs -noaudio

• -logfile -：将日志输出到标准输出，便于实时查看阻塞点
• -force-device-type Null：强制使用Null图形设备，跳过硬件检测
• -disable-gfx-jobs：禁用图形相关的Job系统
• -noaudio：禁用音频子系统，避免不必要的初始化

3. 调整容器权限与资源配置 #

Docker默认权限可能限制Unity执行某些系统调用，尝试：

• 以特权模式启动容器：

  docker run --privileged -d ...
  

• 检查容器的内存、CPU配额，适当调高资源限制，避免初始化阶段资源不足

4. 用strace定位阻塞点 #

在容器内使用strace跟踪进程的系统调用，找到停滞的具体操作：

• 先找到应用的进程ID：ps aux | grep server-headless
• 跟踪系统调用：strace -p <进程ID>
• 或直接用strace启动应用：

  strace ./server-headless-230620-1057 -batchmode -nographics
  

通过系统调用日志可以定位到是等待文件锁、网络连接还是设备访问导致的阻塞。

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