[🐛 Bug ]: exited: log_web_shared (exit status 0; not expected)

[qiushaocloud]

Operating System

ubuntu22.04

Docker Image

budtmo/docker-android:emulator_14.0

Expected behaviour

docker run fail

Actual behaviour

docker run fail

Logs

root@hp-ubuntu2204:/qiushao_apps/android-release# docker run -d -p 6080:6080 -e EMULATOR_DEVICE="Samsung Galaxy S10" -e WEB_VNC=true --device /dev/kvm --name android-container budtmo/docker-android:emulator_14.0
e692cb177752db53315a85ebc4aec6e89f6c1bdc7673ec2f39443e6221ed6769
root@hp-ubuntu2204:/qiushao_apps/android-release# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e692cb177752 budtmo/docker-android:emulator_14.0 "/home/androidusr/do…" 8 seconds ago Up 7 seconds 4723/tcp, 5554-5555/tcp, 5900/tcp, 9000/tcp, 0.0.0.0:6080->6080/tcp, :::6080->6080/tcp android-container
2cb512a063c8 browser-log-upload-master_log-upload-server "node /browser-log-u…" 12 days ago Up 5 hours 0.0.0.0:13080->13080/tcp, :::13080->13080/tcp, 0.0.0.0:13443->13443/tcp, :::13443->13443/tcp log-upload-server
b4d8fd0edb21 minio/minio:latest "/usr/bin/docker-ent…" 4 weeks ago Up 5 hours 0.0.0.0:9000-9001->9000-9001/tcp, :::9000-9001->9000-9001/tcp qiushaocloud-minio
02450c9953e9 registry:2 "/entrypoint.sh /etc…" 2 months ago Up 5 hours 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp qiushaocloud-image-registry
f414f0b765f6 verdaccio/verdaccio "uid_entrypoint /bin…" 2 months ago Up 5 hours 0.0.0.0:4873->4873/tcp, :::4873->4873/tcp qiushaocloud-npmjs-verdaccio
root@hp-ubuntu2204:~/qiushao_apps/android-release# docker logs e692cb177752
2024-07-09 07:32:07,859 INFO supervisord started with pid 8
2024-07-09 07:32:07,863 INFO supervisord started with pid 9
2024-07-09 07:32:07,865 INFO supervisord started with pid 7
2024-07-09 07:32:08,864 INFO spawned: 'android_port_forward' with pid 13
2024-07-09 07:32:08,867 INFO spawned: 'appium' with pid 14
2024-07-09 07:32:08,870 INFO spawned: 'd_screen' with pid 15
2024-07-09 07:32:08,873 INFO spawned: 'device' with pid 16
2024-07-09 07:32:08,876 INFO spawned: 'd_wm' with pid 17
2024-07-09 07:32:08,880 INFO spawned: 'log_web_shared' with pid 18
2024-07-09 07:32:08,884 INFO spawned: 'vnc_server' with pid 19
2024-07-09 07:32:08,891 INFO spawned: 'vnc_web' with pid 20
2024-07-09 07:32:09,867 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-09 07:32:09,885 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-09 07:32:09,886 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-09 07:32:09,886 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-09 07:32:09,897 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-09 07:32:09,898 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-09 07:32:09,898 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-09 07:32:09,898 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-07-09 07:32:10,821 INFO exited: appium (exit status 0; expected)
2024-07-09 07:32:10,822 INFO exited: log_web_shared (exit status 0; expected)
2024-07-09 07:32:11,829 INFO spawned: 'log_web_shared' with pid 65
2024-07-09 07:32:12,487 INFO exited: log_web_shared (exit status 0; not expected)
2024-07-09 07:32:13,494 INFO spawned: 'log_web_shared' with pid 67
2024-07-09 07:32:14,155 INFO exited: log_web_shared (exit status 0; not expected)
2024-07-09 07:32:16,164 INFO spawned: 'log_web_shared' with pid 69
2024-07-09 07:32:16,821 INFO exited: log_web_shared (exit status 0; not expected)
2024-07-09 07:32:19,831 INFO spawned: 'log_web_shared' with pid 71
2024-07-09 07:32:20,497 INFO exited: log_web_shared (exit status 0; not expected)
2024-07-09 07:32:21,500 INFO gave up: log_web_shared entered FATAL state, too many start retries too quickly

[pawlakmaly]

There is an old issue with restarting the docker, try to remove the container and recreate it again

[MrRahulR]

I am also having same issue,restarted docker container even redownloaded the images, but doesn't work unfortunately.

[Chr0nixz]

I have the issue too, but the emulator seemed to be running normally

[jamtheim]

This is a bit sad really. Restaring of docker does not work with persisted data. So whats the point of persisting data? Anybody got a solution. Container is running but it seems webb cant connect. Or rather, it connects but phone screen is gone.

[JyenZhou]

在群晖 DS923+的 DSM7.2上面
我使用
sudo docker run -d -p 10600:6080 -e EMULATOR_DEVICE="Samsung Galaxy S10" -e WEB_VNC=true -v data:/home/androidusr --device /dev/kvm --name android-container budtmo/docker-android
有log_web_shared的错误 容器是正常运行的 但是web访问不了
使用 sudo docker logs android-container 发现有异常log_web_shared entered FATAL state

2024-09-20 05:43:24,022 INFO supervisord started with pid 9
2024-09-20 05:43:24,027 INFO supervisord started with pid 8
2024-09-20 05:43:24,031 INFO supervisord started with pid 7
2024-09-20 05:43:25,024 INFO spawned: 'appium' with pid 13
2024-09-20 05:43:25,025 INFO spawned: 'device' with pid 14
2024-09-20 05:43:25,027 INFO spawned: 'log_web_shared' with pid 15
2024-09-20 05:43:25,029 INFO spawned: 'android_port_forward' with pid 16
2024-09-20 05:43:25,033 INFO spawned: 'd_screen' with pid 17
2024-09-20 05:43:25,035 INFO spawned: 'd_wm' with pid 18
2024-09-20 05:43:25,041 INFO spawned: 'vnc_server' with pid 19
2024-09-20 05:43:25,043 INFO spawned: 'vnc_web' with pid 20
2024-09-20 05:43:26,031 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,035 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,037 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,037 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,044 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,044 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,045 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,045 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,528 INFO exited: vnc_server (exit status 1; not expected)
2024-09-20 05:43:26,536 INFO spawned: 'vnc_server' with pid 48
2024-09-20 05:43:26,580 INFO exited: appium (exit status 0; expected)
2024-09-20 05:43:26,581 INFO exited: log_web_shared (exit status 0; expected)
2024-09-20 05:43:27,583 INFO spawned: 'log_web_shared' with pid 69
2024-09-20 05:43:27,932 INFO exited: log_web_shared (exit status 0; not expected)
2024-09-20 05:43:28,528 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:28,934 INFO spawned: 'log_web_shared' with pid 71
2024-09-20 05:43:29,283 INFO exited: log_web_shared (exit status 0; not expected)
Jyen@NAS:~$ sudo docker logs android-container
2024-09-20 05:43:24,022 INFO supervisord started with pid 9
2024-09-20 05:43:24,027 INFO supervisord started with pid 8
2024-09-20 05:43:24,031 INFO supervisord started with pid 7
2024-09-20 05:43:25,024 INFO spawned: 'appium' with pid 13
2024-09-20 05:43:25,025 INFO spawned: 'device' with pid 14
2024-09-20 05:43:25,027 INFO spawned: 'log_web_shared' with pid 15
2024-09-20 05:43:25,029 INFO spawned: 'android_port_forward' with pid 16
2024-09-20 05:43:25,033 INFO spawned: 'd_screen' with pid 17
2024-09-20 05:43:25,035 INFO spawned: 'd_wm' with pid 18
2024-09-20 05:43:25,041 INFO spawned: 'vnc_server' with pid 19
2024-09-20 05:43:25,043 INFO spawned: 'vnc_web' with pid 20
2024-09-20 05:43:26,031 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,035 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,037 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,037 INFO success: log_web_shared entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,044 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,044 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,045 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,045 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:26,528 INFO exited: vnc_server (exit status 1; not expected)
2024-09-20 05:43:26,536 INFO spawned: 'vnc_server' with pid 48
2024-09-20 05:43:26,580 INFO exited: appium (exit status 0; expected)
2024-09-20 05:43:26,581 INFO exited: log_web_shared (exit status 0; expected)
2024-09-20 05:43:27,583 INFO spawned: 'log_web_shared' with pid 69
2024-09-20 05:43:27,932 INFO exited: log_web_shared (exit status 0; not expected)
2024-09-20 05:43:28,528 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-09-20 05:43:28,934 INFO spawned: 'log_web_shared' with pid 71
2024-09-20 05:43:29,283 INFO exited: log_web_shared (exit status 0; not expected)
2024-09-20 05:43:31,286 INFO spawned: 'log_web_shared' with pid 73
2024-09-20 05:43:31,612 INFO exited: log_web_shared (exit status 0; not expected)
2024-09-20 05:43:34,615 INFO spawned: 'log_web_shared' with pid 75
2024-09-20 05:43:34,906 INFO exited: log_web_shared (exit status 0; not expected)
2024-09-20 05:43:35,907 INFO gave up: log_web_shared entered FATAL state, too many start retries too quickly

另外不支持修改数据保存路径吗
sudo docker run -d -p 10600:6080 -e EMULATOR_DEVICE="Samsung Galaxy S10" -e WEB_VNC=true -v /volume1/JD/Docker/Android/home/androidusr:/home/androidusr --device /dev/kvm --name android-container budtmo/docker-android

docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/home/androidusr/docker-android/mixins/scripts/run.sh": stat /home/androidusr/docker-android/mixins/scripts/run.sh: no such file or directory: unknown.