budtmo
commented
1 year ago Hi @lhincapie0 ,
I am so sorry that I have deleted the old images from docker hub repository. It is because there is changes about user data collection in readme because Google Analytics 3 is shutdown and I need to use alternative for that as Google Analytics 4 is a bit different. To avoid any issue or misunderstanding, I have decided to remove the old images.
Due to a big restructuring to improve the security, efficiency and easy maintenance, I dont think your issue can be fixed here as everything is written in Python now and the old implementation was written in Bash mostly. What my suggestion is you can pull the old codes from this repository, build it locally and push to your local docker hub.
I will close the issue, but feel free to reopen it.
I am so sorry again for the big restructuring that I made.
lhincapie0
jayamvishnudeep
Operating System
Ubuntu
Docker Image
budtmo/docker-android:emulator_12.0
Expected behaviour
Appium should run successfully on the new budtmo/docker-android:emulator_12.0 image and the emulators are started correctly. We can add the configuration missing/changed to run emulators correctly. Could you document which were the changes from one image to another so we can migrate as well? The image budtmo/docker-android-x86-12.0 was really useful for our CI, would really appreciate the help.
Actual behaviour
I was using the budtmo/docker-android-x86-12.0 image to run Appium on our CI, but after the last release and the deletion of the old image, I tried using budtmo/docker-android:emulator_12.0, and it's not working. The emulator does not start. Currently we have the following configuration (with the change of the image):
`app: image: budtmo/docker-android:emulator_12.0 privileged: true scale: 5 depends_on:
Logs
The logs I can see from the image running are:
2023-05-10 11:05:53,993 INFO supervisord started with pid 8 2023-05-10 11:05:53,994 INFO supervisord started with pid 7 2023-05-10 11:05:53,994 INFO supervisord started with pid 9 2023-05-10 11:05:54,995 INFO spawned: 'android_port_forward' with pid 13 2023-05-10 11:05:54,996 INFO spawned: 'appium' with pid 14 2023-05-10 11:05:54,996 INFO spawned: 'd_screen' with pid 15 2023-05-10 11:05:54,997 INFO spawned: 'device' with pid 16 2023-05-10 11:05:54,997 INFO spawned: 'd_wm' with pid 17 2023-05-10 11:05:54,998 INFO spawned: 'vnc_server' with pid 18 2023-05-10 11:05:54,998 INFO spawned: 'log_web_shared' with pid 19 2023-05-10 11:05:54,999 INFO spawned: 'vnc_web' with pid 20 2023-05-10 11:05:55,171 INFO exited: log_web_shared (exit status 0; not expected) 2023-05-10 11:05:55,208 INFO exited: vnc_server (exit status 1; not expected) 2023-05-10 11:05:55,221 INFO exited: d_wm (exit status 1; not expected) 2023-05-10 11:05:56,156 INFO success: d_screen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-05-10 11:05:56,156 INFO success: vnc_web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-05-10 11:05:56,192 INFO success: android_port_forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-05-10 11:05:56,282 INFO success: appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-05-10 11:05:56,282 INFO success: device entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-05-10 11:05:56,283 INFO spawned: 'log_web_shared' with pid 150 2023-05-10 11:05:56,468 INFO exited: log_web_shared (exit status 0; not expected) 2023-05-10 11:05:57,160 INFO spawned: 'd_wm' with pid 198 2023-05-10 11:05:57,161 INFO spawned: 'vnc_server' with pid 199 2023-05-10 11:05:58,409 INFO success: d_wm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-05-10 11:05:58,410 INFO success: vnc_server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-05-10 11:05:58,979 INFO spawned: 'log_web_shared' with pid 298 2023-05-10 11:05:59,127 INFO exited: log_web_shared (exit status 0; not expected) 2023-05-10 11:06:02,430 INFO spawned: 'log_web_shared' with pid 305 2023-05-10 11:06:02,573 INFO exited: log_web_shared (exit status 0; not expected) 2023-05-10 11:06:03,574 INFO gave up: log_web_shared entered FATAL state, too many start retries too quickly