[GH-ISSUE #49] Using Selenium hub I can see my devices but they aren't ON #39

New issue

Closed

opened 2026-03-01 15:39:35 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 15:39:35 +03:00

Owner

Originally created by @lepadellec on GitHub (Nov 16, 2017).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/49

I am using docker-compose to bring up 3 different devices
butomo1989/docker-android-x86-7.0
butomo1989/docker-android-x86-7.1.1
butomo1989/docker-android-x86-5.1.1

when I connect to the different noVNC windows I see my appium server (I want to automate some appium tests) and I see my device but clearly the device isn't on, if I press the ON button in the control panel this makes no difference. When I try to launch my tests and start my own APK clearly this doesn't work. When I look at the docker log I see:
docker exec -it laura_nexus_7.0_1 tail -f /var/log/supervisor/docker-android.stdout.log
Journal blocks: 1024
Label:
Blocks: 16896
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4224 inodes and 1302/16896 blocks
emulator: warning: opening audio output failed

emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554

Any help would be greatly appreciated.
Host: docker info gives:
Containers: 4
Running: 4
Paused: 0
Stopped: 0
Images: 4
Server Version: 1.12.2
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 60
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: overlay null bridge host
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.10.8-docker-1
Operating System: Ubuntu 16.04.3 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.857 GiB
Name: iw-qa-appium
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
provider=scaleway
Insecure Registries:
127.0.0.0/8

Originally created by @lepadellec on GitHub (Nov 16, 2017). Original GitHub issue: https://github.com/budtmo/docker-android/issues/49 I am using docker-compose to bring up 3 different devices butomo1989/docker-android-x86-7.0 butomo1989/docker-android-x86-7.1.1 butomo1989/docker-android-x86-5.1.1 when I connect to the different noVNC windows I see my appium server (I want to automate some appium tests) and I see my device but clearly the device isn't on, if I press the ON button in the control panel this makes no difference. When I try to launch my tests and start my own APK clearly this doesn't work. When I look at the docker log I see: docker exec -it laura_nexus_7.0_1 tail -f /var/log/supervisor/docker-android.stdout.log Journal blocks: 1024 Label: Blocks: 16896 Block groups: 1 Reserved block group size: 7 Created filesystem with 11/4224 inodes and 1302/16896 blocks emulator: warning: opening audio output failed emulator: Listening for console connections on port: 5554 emulator: Serial number of this emulator (for ADB): emulator-5554 Any help would be greatly appreciated. Host: docker info gives: Containers: 4 Running: 4 Paused: 0 Stopped: 0 Images: 4 Server Version: 1.12.2 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 60 Dirperm1 Supported: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: overlay null bridge host Swarm: inactive Runtimes: runc Default Runtime: runc Security Options: seccomp Kernel Version: 4.10.8-docker-1 Operating System: Ubuntu 16.04.3 LTS OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 3.857 GiB Name: iw-qa-appium Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: provider=scaleway Insecure Registries: 127.0.0.0/8