[GH-ISSUE #220] Cannot run on Digital Ocean Kubernetes #162

New issue

Closed

opened 2026-03-01 15:41:02 +03:00 by kerem · 1 comment

kerem commented

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

Owner

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

🐛 Bug Report

Operating System:
Debian 1.15

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

I am exposing 80 on host port to map to 6080 on container.
and browse http://host_ip, nothing is served there

Logs

2019-12-18 22:12:12,162 CRIT Supervisor running as root (no user in config file)

2019-12-18 22:12:12,167 INFO supervisord started with pid 6

2019-12-18 22:12:13,171 INFO spawned: 'xvfb' with pid 9

2019-12-18 22:12:13,174 INFO spawned: 'port-forward' with pid 10

2019-12-18 22:12:13,177 INFO spawned: 'novnc' with pid 11

2019-12-18 22:12:13,179 INFO spawned: 'openbox' with pid 12

2019-12-18 22:12:13,184 INFO spawned: 'x11vnc' with pid 13

2019-12-18 22:12:13,189 INFO spawned: 'screen-copy' with pid 14

2019-12-18 22:12:13,196 INFO spawned: 'docker-appium' with pid 17

2019-12-18 22:12:13,204 INFO spawned: 'atd' with pid 23

2019-12-18 22:12:13,232 INFO spawned: 'auto-recording' with pid 33

2019-12-18 22:12:13,246 INFO spawned: 'adb-utils' with pid 42

2019-12-18 22:12:13,247 INFO exited: screen-copy (exit status 0; not expected)

2019-12-18 22:12:13,248 INFO exited: atd (exit status 0; not expected)

2019-12-18 22:12:14,270 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2019-12-18 22:12:14,271 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2019-12-18 22:12:14,271 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2019-12-18 22:12:14,272 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2019-12-18 22:12:14,272 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2019-12-18 22:12:14,274 INFO spawned: 'screen-copy' with pid 114

2019-12-18 22:12:14,275 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2019-12-18 22:12:14,277 INFO spawned: 'atd' with pid 116

2019-12-18 22:12:14,278 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2019-12-18 22:12:14,278 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2019-12-18 22:12:14,292 INFO exited: screen-copy (exit status 0; not expected)

2019-12-18 22:12:14,302 INFO exited: atd (exit status 0; not expected)

2019-12-18 22:12:16,297 INFO spawned: 'screen-copy' with pid 126

2019-12-18 22:12:16,309 INFO spawned: 'atd' with pid 127

2019-12-18 22:12:16,311 INFO exited: screen-copy (exit status 0; not expected)

2019-12-18 22:12:16,317 INFO exited: atd (exit status 0; not expected)

2019-12-18 22:12:19,276 INFO exited: auto-recording (exit status 0; expected)

2019-12-18 22:12:20,281 INFO spawned: 'screen-copy' with pid 129

2019-12-18 22:12:20,289 INFO spawned: 'atd' with pid 130

2019-12-18 22:12:20,297 INFO exited: atd (exit status 0; not expected)

2019-12-18 22:12:20,301 INFO gave up: atd entered FATAL state, too many start retries too quickly

2019-12-18 22:12:20,301 INFO exited: screen-copy (exit status 0; not expected)

2019-12-18 22:12:20,301 INFO gave up: screen-copy entered FATAL state, too many start retries too quickly

2019-12-18 22:12:40,597 INFO exited: docker-appium (exit status 0; expected)

Originally created by @marufbd on GitHub (Dec 19, 2019). Original GitHub issue: https://github.com/budtmo/docker-android/issues/220 ## 🐛 Bug Report Operating System: Debian 1.15 Docker Image: budtmo/docker-android-x86-6.0 I am exposing 80 on host port to map to 6080 on container. and browse http://host_ip, nothing is served there ## Logs ``` 2019-12-18 22:12:12,162 CRIT Supervisor running as root (no user in config file) 2019-12-18 22:12:12,167 INFO supervisord started with pid 6 2019-12-18 22:12:13,171 INFO spawned: 'xvfb' with pid 9 2019-12-18 22:12:13,174 INFO spawned: 'port-forward' with pid 10 2019-12-18 22:12:13,177 INFO spawned: 'novnc' with pid 11 2019-12-18 22:12:13,179 INFO spawned: 'openbox' with pid 12 2019-12-18 22:12:13,184 INFO spawned: 'x11vnc' with pid 13 2019-12-18 22:12:13,189 INFO spawned: 'screen-copy' with pid 14 2019-12-18 22:12:13,196 INFO spawned: 'docker-appium' with pid 17 2019-12-18 22:12:13,204 INFO spawned: 'atd' with pid 23 2019-12-18 22:12:13,232 INFO spawned: 'auto-recording' with pid 33 2019-12-18 22:12:13,246 INFO spawned: 'adb-utils' with pid 42 2019-12-18 22:12:13,247 INFO exited: screen-copy (exit status 0; not expected) 2019-12-18 22:12:13,248 INFO exited: atd (exit status 0; not expected) 2019-12-18 22:12:14,270 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-12-18 22:12:14,271 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-12-18 22:12:14,271 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-12-18 22:12:14,272 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-12-18 22:12:14,272 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-12-18 22:12:14,274 INFO spawned: 'screen-copy' with pid 114 2019-12-18 22:12:14,275 INFO success: docker-appium entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-12-18 22:12:14,277 INFO spawned: 'atd' with pid 116 2019-12-18 22:12:14,278 INFO success: auto-recording entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-12-18 22:12:14,278 INFO success: adb-utils entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-12-18 22:12:14,292 INFO exited: screen-copy (exit status 0; not expected) 2019-12-18 22:12:14,302 INFO exited: atd (exit status 0; not expected) 2019-12-18 22:12:16,297 INFO spawned: 'screen-copy' with pid 126 2019-12-18 22:12:16,309 INFO spawned: 'atd' with pid 127 2019-12-18 22:12:16,311 INFO exited: screen-copy (exit status 0; not expected) 2019-12-18 22:12:16,317 INFO exited: atd (exit status 0; not expected) 2019-12-18 22:12:19,276 INFO exited: auto-recording (exit status 0; expected) 2019-12-18 22:12:20,281 INFO spawned: 'screen-copy' with pid 129 2019-12-18 22:12:20,289 INFO spawned: 'atd' with pid 130 2019-12-18 22:12:20,297 INFO exited: atd (exit status 0; not expected) 2019-12-18 22:12:20,301 INFO gave up: atd entered FATAL state, too many start retries too quickly 2019-12-18 22:12:20,301 INFO exited: screen-copy (exit status 0; not expected) 2019-12-18 22:12:20,301 INFO gave up: screen-copy entered FATAL state, too many start retries too quickly 2019-12-18 22:12:40,597 INFO exited: docker-appium (exit status 0; expected) ```

kerem closed this issue

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

kerem commented

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

Author

Owner

@budtmo commented on GitHub (Jan 7, 2020):

Hi @marufbd ,

I never tried that, but you need to make sure that the machine support Virtualization and it must work. I will close the ticket for now.

@budtmo commented on GitHub (Jan 7, 2020): Hi @marufbd , I never tried that, but you need to make sure that the machine support Virtualization and it must work. I will close the ticket for now.