[🐛 Bug ]: 使用docker compose启动文件会导致容器一直处于重启状态 #562
Description
Operating System
win11‘sub system wsl ubuntu24.04
Docker Image
budtmo/docker-android:emulator_14.0
Expected behaviour
容器启动后按预期加载安卓镜像，启动安卓虚拟机
docker compose文件内容：
定义 Docker Compose 版本（建议指定，提升兼容性）
version: '3.8'
services:
android-container:
container_name: android-container
image: budtmo/docker-android:emulator_14.0
ports:
- 7080:6080 # 将容器的6080端口（VNC WEB）映射到主机7080
environment:
- EMULATOR_DEVICE=Samsung Galaxy S10 # 移除多余的双引号，避免值包含引号
- WEB_VNC=true
volumes:
# 方式1：使用命名卷持久化容器内/home/androidusr目录（推荐）
- android-data:/home/androidusr
# # 方式2：如果需要将模拟器镜像持久化到主机指定路径，取消下面注释并替换/your/host/path
# # - /your/host/path/android-system-images:/opt/android/system-images
devices:
- /dev/kvm # 挂载KVM，需要主机开启虚拟化，否则模拟器极慢
# # 可选：添加重启策略，容器异常退出时自动重启
# restart: unless-stopped
volumes:
android-data:
# # 数据卷的driver应为存储驱动（如local），而非路径；若要指定存储路径，需用driver_opts
# driver: local
# 可选：将命名卷存储到主机指定路径（需确保路径存在且有权限）
driver_opts:
type: none
o: bind
device: ${WORKPATH}
Actual behaviour
如日志，一直重启
Logs
time="2026-01-16T14:12:33+08:00" level=warning msg="/mnt/d/ProgramData/CommandTools/WSL/volumes/dpanel/compose/android/docker-compose.yaml: the attribute version is obsolete, it will be ignored, please remove it to avoid potential confusion"
android-container | 2026-01-16 06:12:29,931 INFO supervisord started with pid 8
android-container | 2026-01-16 06:12:29,934 INFO supervisord started with pid 7
android-container | 2026-01-16 06:12:29,936 INFO supervisord started with pid 9
android-container | 2026-01-16 06:12:30,942 INFO spawned: 'android_port_forward' with pid 10
android-container | 2026-01-16 06:12:30,944 INFO spawned: 'd_screen' with pid 11
android-container | 2026-01-16 06:12:30,945 INFO spawned: 'appium' with pid 12
android-container | 2026-01-16 06:12:30,952 INFO spawned: 'device' with pid 13
android-container | 2026-01-16 06:12:30,956 INFO spawned: 'd_wm' with pid 14
android-container | 2026-01-16 06:12:30,965 INFO spawned: 'log_web_shared' with pid 15
android-container | 2026-01-16 06:12:30,966 INFO spawned: 'vnc_server' with pid 16
android-container | 2026-01-16 06:12:30,979 INFO spawned: 'vnc_web' with pid 17
android-container | 2026-01-16 06:12:31,944 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:31,968 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:31,971 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:31,975 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:31,982 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:31,982 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:31,983 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:31,984 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:32,826 INFO exited: appium (exit status 0; expected)
android-container | 2026-01-16 06:12:32,827 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:12:33,837 INFO spawned: 'log_web_shared' with pid 53
android-container | 2026-01-16 06:12:34,839 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:36,313 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:12:37,329 INFO spawned: 'log_web_shared' with pid 57
android-container | 2026-01-16 06:12:38,331 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:39,801 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:12:40,814 INFO spawned: 'log_web_shared' with pid 58
android-container | 2026-01-16 06:12:41,817 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:43,245 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:12:44,263 INFO spawned: 'log_web_shared' with pid 59
android-container | 2026-01-16 06:12:45,266 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:46,947 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:12:47,979 INFO spawned: 'log_web_shared' with pid 60
android-container | 2026-01-16 06:12:48,982 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:50,328 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:12:51,339 INFO spawned: 'log_web_shared' with pid 61
android-container | 2026-01-16 06:12:52,341 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:53,667 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:12:54,677 INFO spawned: 'log_web_shared' with pid 62
android-container | 2026-01-16 06:12:55,679 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:12:57,056 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:12:58,068 INFO spawned: 'log_web_shared' with pid 63
android-container | 2026-01-16 06:12:59,070 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:13:00,739 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:13:01,758 INFO spawned: 'log_web_shared' with pid 64
android-container | 2026-01-16 06:13:02,761 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:13:04,502 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:13:05,532 INFO spawned: 'log_web_shared' with pid 65
android-container | 2026-01-16 06:13:06,535 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:13:08,338 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:13:09,357 INFO spawned: 'log_web_shared' with pid 66
android-container | 2026-01-16 06:13:10,360 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:13:11,903 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:13:12,916 INFO spawned: 'log_web_shared' with pid 67
android-container | 2026-01-16 06:13:13,918 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
android-container | 2026-01-16 06:13:15,264 INFO exited: log_web_shared (exit status 0; expected)
android-container | 2026-01-16 06:13:16,287 INFO spawned: 'log_web_shared' with pid 68