[GH-ISSUE #192] Emulator not displaying in noVNC view #135

New issue

Closed

opened 2026-03-01 15:40:48 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 15:40:48 +03:00

Owner

Originally created by @gepsl on GitHub (Aug 22, 2019).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/192

I want to build test automation infrastructure on Centos7 using docker. In order to do that I'm using docker-compose file. I want to run selenium hub, docker-chrome node and docker-android node. Hub and chrome node starting correctly, but emulator is not displaying after connect to server_ip:6080. I can see only appium server logs and emulator terminal. It's seems like emulator start opening but closing after 1/2 second (window with emulator displaying and closing after that). In docker container logs can see that something with atd is wrong.

docker-compose file:

version: "3.7"

services:
  selenium_hub:
    image: selenium/hub:3.141.59-titanium
    ports:
      - 4444:4444

  samsung_galaxy_s6:
    image: budtmo/docker-android-x86-8.1
    privileged: true
    depends_on:
      - selenium_hub
    ports:
      - 6080:6080
      - 5555:5555
      - 5554:5554
      - 4723:4723
    volumes:
      - /lastore_app/LAStore4:/lastore_app
    environment:
      - DEVICE=Samsung Galaxy S6
      - CONNECT_TO_GRID=true
      - APPIUM=true
      - SELENIUM_HOST=selenium_hub
      - MOBILE_WEB_TEST=true
      - ATD=true
      
  chrome:
    image: selenium/node-chrome:3.141.59-titanium
    volumes:
      - /dev/shm:/dev/shm
    depends_on:
      - selenium_hub
    environment:
      - HUB_HOST=selenium_hub
      - START_XVFB=false

docker container logs:

2019-08-22 07:03:30,587 CRIT Supervisor running as root (no user in config file)
2019-08-22 07:03:30,605 INFO supervisord started with pid 6
2019-08-22 07:03:31,614 INFO spawned: 'xvfb' with pid 9
2019-08-22 07:03:31,617 INFO spawned: 'port-forward' with pid 10
2019-08-22 07:03:31,623 INFO spawned: 'novnc' with pid 11
2019-08-22 07:03:31,626 INFO spawned: 'openbox' with pid 12
2019-08-22 07:03:31,650 INFO spawned: 'x11vnc' with pid 14
2019-08-22 07:03:31,667 INFO spawned: 'android-screen-mirror' with pid 17
2019-08-22 07:03:31,670 INFO spawned: 'docker-appium' with pid 18
2019-08-22 07:03:31,687 INFO spawned: 'atd' with pid 19
2019-08-22 07:03:31,713 INFO spawned: 'auto-recording' with pid 25
2019-08-22 07:03:31,719 INFO spawned: 'adb-utils' with pid 26
2019-08-22 07:03:31,771 INFO success: android-screen-mirror entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-08-22 07:03:31,781 INFO exited: android-screen-mirror (exit status 0; expected)
2019-08-22 07:03:31,805 INFO exited: atd (exit status 0; not expected)
2019-08-22 07:03:32,674 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-22 07:03:32,674 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-22 07:03:32,674 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-22 07:03:32,674 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-22 07:03:32,674 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-22 07:03:32,674 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-22 07:03:32,888 INFO spawned: 'atd' with pid 124
2019-08-22 07:03:32,888 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-22 07:03:32,888 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-22 07:03:32,901 INFO exited: atd (exit status 0; not expected)
2019-08-22 07:03:34,914 INFO spawned: 'atd' with pid 135
2019-08-22 07:03:34,932 INFO exited: atd (exit status 0; not expected)
2019-08-22 07:03:37,859 INFO exited: auto-recording (exit status 0; expected)
2019-08-22 07:03:37,986 INFO spawned: 'atd' with pid 140
2019-08-22 07:03:37,991 INFO exited: atd (exit status 0; not expected)
2019-08-22 07:03:38,085 INFO gave up: atd entered FATAL state, too many start retries too quickly

Originally created by @gepsl on GitHub (Aug 22, 2019). Original GitHub issue: https://github.com/budtmo/docker-android/issues/192 I want to build test automation infrastructure on Centos7 using docker. In order to do that I'm using docker-compose file. I want to run selenium hub, docker-chrome node and docker-android node. Hub and chrome node starting correctly, but emulator is not displaying after connect to server_ip:6080. I can see only appium server logs and emulator terminal. It's seems like emulator start opening but closing after 1/2 second (window with emulator displaying and closing after that). In docker container logs can see that something with atd is wrong. **docker-compose file:** ``` version: "3.7" services: selenium_hub: image: selenium/hub:3.141.59-titanium ports: - 4444:4444 samsung_galaxy_s6: image: budtmo/docker-android-x86-8.1 privileged: true depends_on: - selenium_hub ports: - 6080:6080 - 5555:5555 - 5554:5554 - 4723:4723 volumes: - /lastore_app/LAStore4:/lastore_app environment: - DEVICE=Samsung Galaxy S6 - CONNECT_TO_GRID=true - APPIUM=true - SELENIUM_HOST=selenium_hub - MOBILE_WEB_TEST=true - ATD=true chrome: image: selenium/node-chrome:3.141.59-titanium volumes: - /dev/shm:/dev/shm depends_on: - selenium_hub environment: - HUB_HOST=selenium_hub - START_XVFB=false ``` **docker container logs:** ``` 2019-08-22 07:03:30,587 CRIT Supervisor running as root (no user in config file) 2019-08-22 07:03:30,605 INFO supervisord started with pid 6 2019-08-22 07:03:31,614 INFO spawned: 'xvfb' with pid 9 2019-08-22 07:03:31,617 INFO spawned: 'port-forward' with pid 10 2019-08-22 07:03:31,623 INFO spawned: 'novnc' with pid 11 2019-08-22 07:03:31,626 INFO spawned: 'openbox' with pid 12 2019-08-22 07:03:31,650 INFO spawned: 'x11vnc' with pid 14 2019-08-22 07:03:31,667 INFO spawned: 'android-screen-mirror' with pid 17 2019-08-22 07:03:31,670 INFO spawned: 'docker-appium' with pid 18 2019-08-22 07:03:31,687 INFO spawned: 'atd' with pid 19 2019-08-22 07:03:31,713 INFO spawned: 'auto-recording' with pid 25 2019-08-22 07:03:31,719 INFO spawned: 'adb-utils' with pid 26 2019-08-22 07:03:31,771 INFO success: android-screen-mirror entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-08-22 07:03:31,781 INFO exited: android-screen-mirror (exit status 0; expected) 2019-08-22 07:03:31,805 INFO exited: atd (exit status 0; not expected) 2019-08-22 07:03:32,674 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-08-22 07:03:32,674 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-08-22 07:03:32,674 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-08-22 07:03:32,674 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-08-22 07:03:32,674 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-08-22 07:03:32,674 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-08-22 07:03:32,888 INFO spawned: 'atd' with pid 124 2019-08-22 07:03:32,888 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-08-22 07:03:32,888 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-08-22 07:03:32,901 INFO exited: atd (exit status 0; not expected) 2019-08-22 07:03:34,914 INFO spawned: 'atd' with pid 135 2019-08-22 07:03:34,932 INFO exited: atd (exit status 0; not expected) 2019-08-22 07:03:37,859 INFO exited: auto-recording (exit status 0; expected) 2019-08-22 07:03:37,986 INFO spawned: 'atd' with pid 140 2019-08-22 07:03:37,991 INFO exited: atd (exit status 0; not expected) 2019-08-22 07:03:38,085 INFO gave up: atd entered FATAL state, too many start retries too quickly ```

kerem closed this issue

2026-03-01 15:40:49 +03:00

kerem commented

2026-03-01 15:40:49 +03:00

Author

Owner

@mcopjan commented on GitHub (Aug 22, 2019):

The same for me on CentOs. I did not hook it up with a selenium grid, but tried to VNC into the container and emulator was never displayed. I tried with budtmo/docker-android-x86-8.0 , 8.1 and 9.0

@mcopjan commented on GitHub (Aug 22, 2019): The same for me on CentOs. I did not hook it up with a selenium grid, but tried to VNC into the container and emulator was never displayed. I tried with budtmo/docker-android-x86-8.0 , 8.1 and 9.0

kerem commented

2026-03-01 15:40:49 +03:00

Author

Owner

@budtmo commented on GitHub (Aug 22, 2019):

duplicated #93

@budtmo commented on GitHub (Aug 22, 2019): duplicated #93