[GH-ISSUE #222] Running emulator crashes #161

New issue

Closed

opened 2026-03-01 15:41:02 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 15:41:02 +03:00

Owner

Originally created by @AlexanderQuack on GitHub (Dec 27, 2019).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/222

🐛 Bug Report

Running emulator crashes. Docker restart container starts again emulator, but not for long.

Operating System:
Ubuntu 18.04

Docker Image:
budtmo/docker-android-x86-9.0

Docker Version:
18.09.7

Docker Command to start docker-android:
docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -p 4723:4723 -e DEVICE="Samsung Galaxy S6" -e APPIUM=true --name android-container budtmo/docker-android-x86-9.0

docker-android.stderr.log
docker-android.stdout.log
supervisord.log

Originally created by @AlexanderQuack on GitHub (Dec 27, 2019). Original GitHub issue: https://github.com/budtmo/docker-android/issues/222 ## 🐛 Bug Report Running emulator crashes. Docker restart container starts again emulator, but not for long. Operating System: Ubuntu 18.04 Docker Image: budtmo/docker-android-x86-9.0 Docker Version: 18.09.7 Docker Command to start docker-android: docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -p 4723:4723 -e DEVICE="Samsung Galaxy S6" -e APPIUM=true --name android-container budtmo/docker-android-x86-9.0 [docker-android.stderr.log](https://github.com/budtmo/docker-android/files/4005641/docker-android.stderr.log) [docker-android.stdout.log](https://github.com/budtmo/docker-android/files/4005642/docker-android.stdout.log) [supervisord.log](https://github.com/budtmo/docker-android/files/4005643/supervisord.log)

kerem closed this issue

2026-03-01 15:41:02 +03:00

kerem commented

2026-03-01 15:41:03 +03:00

Author

Owner

@ilteoood commented on GitHub (Jan 26, 2020):

Same problem here.
In my case, even restarting the container doesn't bring back the emulator, I have to delete the container and create a new one

@ilteoood commented on GitHub (Jan 26, 2020): Same problem here. In my case, even restarting the container doesn't bring back the emulator, I have to delete the container and create a new one

kerem commented

2026-03-01 15:41:03 +03:00

Author

Owner

@AlexanderQuack commented on GitHub (Jan 30, 2020):

I have new case of crashes:
supervisord.log

2020-01-29 21:28:04,314 CRIT Supervisor running as root (no user in config file)
2020-01-29 21:28:04,317 INFO supervisord started with pid 6
2020-01-29 21:28:05,320 INFO spawned: 'xvfb' with pid 9
2020-01-29 21:28:05,322 INFO spawned: 'port-forward' with pid 10
2020-01-29 21:28:05,324 INFO spawned: 'novnc' with pid 11
2020-01-29 21:28:05,325 INFO spawned: 'openbox' with pid 12
2020-01-29 21:28:05,328 INFO spawned: 'x11vnc' with pid 13
2020-01-29 21:28:05,329 INFO spawned: 'screen-copy' with pid 15
2020-01-29 21:28:05,330 INFO spawned: 'docker-appium' with pid 17
2020-01-29 21:28:05,331 INFO spawned: 'atd' with pid 22
2020-01-29 21:28:05,333 INFO spawned: 'auto-recording' with pid 25
2020-01-29 21:28:05,334 INFO spawned: 'adb-utils' with pid 28
2020-01-29 21:28:05,334 INFO exited: xvfb (exit status 1; not expected)
2020-01-29 21:28:05,337 INFO exited: screen-copy (exit status 0; not expected)
2020-01-29 21:28:05,337 INFO exited: atd (exit status 0; not expected)
2020-01-29 21:28:05,342 INFO exited: openbox (exit status 1; not expected)
2020-01-29 21:28:05,343 INFO exited: x11vnc (exit status 1; not expected)
2020-01-29 21:28:05,512 INFO exited: docker-appium (exit status 1; not expected)
2020-01-29 21:28:06,366 INFO spawned: 'xvfb' with pid 82
2020-01-29 21:28:06,367 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-29 21:28:06,367 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-29 21:28:06,368 INFO spawned: 'openbox' with pid 84
2020-01-29 21:28:06,370 INFO spawned: 'x11vnc' with pid 85
2020-01-29 21:28:06,371 INFO spawned: 'screen-copy' with pid 86
2020-01-29 21:28:06,373 INFO spawned: 'atd' with pid 87
2020-01-29 21:28:06,374 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-29 21:28:06,374 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-01-29 21:28:06,378 INFO exited: xvfb (exit status 1; not expected)
2020-01-29 21:28:06,379 INFO exited: screen-copy (exit status 0; not expected)
2020-01-29 21:28:06,381 INFO exited: atd (exit status 0; not expected)
2020-01-29 21:28:06,385 INFO exited: x11vnc (exit status 1; not expected)
2020-01-29 21:28:06,391 INFO exited: openbox (exit status 1; not expected)
2020-01-29 21:28:07,393 INFO spawned: 'docker-appium' with pid 93
2020-01-29 21:28:07,598 INFO exited: docker-appium (exit status 1; not expected)
2020-01-29 21:28:08,601 INFO spawned: 'xvfb' with pid 118
2020-01-29 21:28:08,603 INFO spawned: 'openbox' with pid 119
2020-01-29 21:28:08,604 INFO spawned: 'x11vnc' with pid 120
2020-01-29 21:28:08,606 INFO spawned: 'screen-copy' with pid 121
2020-01-29 21:28:08,607 INFO spawned: 'atd' with pid 122
2020-01-29 21:28:08,612 INFO exited: xvfb (exit status 1; not expected)
2020-01-29 21:28:08,614 INFO exited: screen-copy (exit status 0; not expected)
2020-01-29 21:28:08,615 INFO exited: atd (exit status 0; not expected)
2020-01-29 21:28:08,620 INFO exited: x11vnc (exit status 1; not expected)
2020-01-29 21:28:08,625 INFO exited: openbox (exit status 1; not expected)
2020-01-29 21:28:09,628 INFO spawned: 'docker-appium' with pid 125
2020-01-29 21:28:09,820 INFO exited: docker-appium (exit status 1; not expected)
2020-01-29 21:28:11,344 INFO exited: auto-recording (exit status 0; expected)
2020-01-29 21:28:12,347 INFO spawned: 'xvfb' with pid 150
2020-01-29 21:28:12,349 INFO spawned: 'openbox' with pid 151
2020-01-29 21:28:12,350 INFO spawned: 'x11vnc' with pid 152
2020-01-29 21:28:12,352 INFO spawned: 'screen-copy' with pid 153
2020-01-29 21:28:12,354 INFO spawned: 'atd' with pid 154
2020-01-29 21:28:12,358 INFO exited: xvfb (exit status 1; not expected)
2020-01-29 21:28:12,360 INFO gave up: xvfb entered FATAL state, too many start retries too quickly
2020-01-29 21:28:12,360 INFO exited: screen-copy (exit status 0; not expected)
2020-01-29 21:28:12,361 INFO gave up: screen-copy entered FATAL state, too many start retries too quickly
2020-01-29 21:28:12,362 INFO exited: atd (exit status 0; not expected)
2020-01-29 21:28:12,365 INFO gave up: atd entered FATAL state, too many start retries too quickly
2020-01-29 21:28:12,366 INFO exited: x11vnc (exit status 1; not expected)
2020-01-29 21:28:12,368 INFO gave up: x11vnc entered FATAL state, too many start retries too quickly
2020-01-29 21:28:12,369 INFO exited: openbox (exit status 1; not expected)
2020-01-29 21:28:13,370 INFO gave up: openbox entered FATAL state, too many start retries too quickly
2020-01-29 21:28:13,372 INFO spawned: 'docker-appium' with pid 156
2020-01-29 21:28:13,553 INFO exited: docker-appium (exit status 1; not expected)
2020-01-29 21:28:13,554 INFO gave up: docker-appium entered FATAL state, too many start retries too quickly

xvfb.stderr.log

Using O_TMPFILE
Using O_TMPFILE
Using O_TMPFILE
Using O_TMPFILE
(EE) 
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE) 
(EE) 
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE) 
(EE) 
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE) 
(EE) 
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE) 
(EE) 
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE) 
(EE) 
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE) 
(EE) 
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE) 
(EE) 
Fatal server error:
(EE) Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.
(EE)

for me docker exec -it ${containerName} rm -f /tmp/.X0-lock fix it

@AlexanderQuack commented on GitHub (Jan 30, 2020): I have new case of crashes: supervisord.log ``` 2020-01-29 21:28:04,314 CRIT Supervisor running as root (no user in config file) 2020-01-29 21:28:04,317 INFO supervisord started with pid 6 2020-01-29 21:28:05,320 INFO spawned: 'xvfb' with pid 9 2020-01-29 21:28:05,322 INFO spawned: 'port-forward' with pid 10 2020-01-29 21:28:05,324 INFO spawned: 'novnc' with pid 11 2020-01-29 21:28:05,325 INFO spawned: 'openbox' with pid 12 2020-01-29 21:28:05,328 INFO spawned: 'x11vnc' with pid 13 2020-01-29 21:28:05,329 INFO spawned: 'screen-copy' with pid 15 2020-01-29 21:28:05,330 INFO spawned: 'docker-appium' with pid 17 2020-01-29 21:28:05,331 INFO spawned: 'atd' with pid 22 2020-01-29 21:28:05,333 INFO spawned: 'auto-recording' with pid 25 2020-01-29 21:28:05,334 INFO spawned: 'adb-utils' with pid 28 2020-01-29 21:28:05,334 INFO exited: xvfb (exit status 1; not expected) 2020-01-29 21:28:05,337 INFO exited: screen-copy (exit status 0; not expected) 2020-01-29 21:28:05,337 INFO exited: atd (exit status 0; not expected) 2020-01-29 21:28:05,342 INFO exited: openbox (exit status 1; not expected) 2020-01-29 21:28:05,343 INFO exited: x11vnc (exit status 1; not expected) 2020-01-29 21:28:05,512 INFO exited: docker-appium (exit status 1; not expected) 2020-01-29 21:28:06,366 INFO spawned: 'xvfb' with pid 82 2020-01-29 21:28:06,367 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-01-29 21:28:06,367 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-01-29 21:28:06,368 INFO spawned: 'openbox' with pid 84 2020-01-29 21:28:06,370 INFO spawned: 'x11vnc' with pid 85 2020-01-29 21:28:06,371 INFO spawned: 'screen-copy' with pid 86 2020-01-29 21:28:06,373 INFO spawned: 'atd' with pid 87 2020-01-29 21:28:06,374 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-01-29 21:28:06,374 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-01-29 21:28:06,378 INFO exited: xvfb (exit status 1; not expected) 2020-01-29 21:28:06,379 INFO exited: screen-copy (exit status 0; not expected) 2020-01-29 21:28:06,381 INFO exited: atd (exit status 0; not expected) 2020-01-29 21:28:06,385 INFO exited: x11vnc (exit status 1; not expected) 2020-01-29 21:28:06,391 INFO exited: openbox (exit status 1; not expected) 2020-01-29 21:28:07,393 INFO spawned: 'docker-appium' with pid 93 2020-01-29 21:28:07,598 INFO exited: docker-appium (exit status 1; not expected) 2020-01-29 21:28:08,601 INFO spawned: 'xvfb' with pid 118 2020-01-29 21:28:08,603 INFO spawned: 'openbox' with pid 119 2020-01-29 21:28:08,604 INFO spawned: 'x11vnc' with pid 120 2020-01-29 21:28:08,606 INFO spawned: 'screen-copy' with pid 121 2020-01-29 21:28:08,607 INFO spawned: 'atd' with pid 122 2020-01-29 21:28:08,612 INFO exited: xvfb (exit status 1; not expected) 2020-01-29 21:28:08,614 INFO exited: screen-copy (exit status 0; not expected) 2020-01-29 21:28:08,615 INFO exited: atd (exit status 0; not expected) 2020-01-29 21:28:08,620 INFO exited: x11vnc (exit status 1; not expected) 2020-01-29 21:28:08,625 INFO exited: openbox (exit status 1; not expected) 2020-01-29 21:28:09,628 INFO spawned: 'docker-appium' with pid 125 2020-01-29 21:28:09,820 INFO exited: docker-appium (exit status 1; not expected) 2020-01-29 21:28:11,344 INFO exited: auto-recording (exit status 0; expected) 2020-01-29 21:28:12,347 INFO spawned: 'xvfb' with pid 150 2020-01-29 21:28:12,349 INFO spawned: 'openbox' with pid 151 2020-01-29 21:28:12,350 INFO spawned: 'x11vnc' with pid 152 2020-01-29 21:28:12,352 INFO spawned: 'screen-copy' with pid 153 2020-01-29 21:28:12,354 INFO spawned: 'atd' with pid 154 2020-01-29 21:28:12,358 INFO exited: xvfb (exit status 1; not expected) 2020-01-29 21:28:12,360 INFO gave up: xvfb entered FATAL state, too many start retries too quickly 2020-01-29 21:28:12,360 INFO exited: screen-copy (exit status 0; not expected) 2020-01-29 21:28:12,361 INFO gave up: screen-copy entered FATAL state, too many start retries too quickly 2020-01-29 21:28:12,362 INFO exited: atd (exit status 0; not expected) 2020-01-29 21:28:12,365 INFO gave up: atd entered FATAL state, too many start retries too quickly 2020-01-29 21:28:12,366 INFO exited: x11vnc (exit status 1; not expected) 2020-01-29 21:28:12,368 INFO gave up: x11vnc entered FATAL state, too many start retries too quickly 2020-01-29 21:28:12,369 INFO exited: openbox (exit status 1; not expected) 2020-01-29 21:28:13,370 INFO gave up: openbox entered FATAL state, too many start retries too quickly 2020-01-29 21:28:13,372 INFO spawned: 'docker-appium' with pid 156 2020-01-29 21:28:13,553 INFO exited: docker-appium (exit status 1; not expected) 2020-01-29 21:28:13,554 INFO gave up: docker-appium entered FATAL state, too many start retries too quickly ``` xvfb.stderr.log ``` Using O_TMPFILE Using O_TMPFILE Using O_TMPFILE Using O_TMPFILE (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) ``` for me `docker exec -it ${containerName} rm -f /tmp/.X0-lock` fix it