Closed SudhanvaManjunath closed 1 year ago
I have the same problem here.
I'm using Ubuntu
Update: It worked when I removed EMULATOR_ADDITIONAL_ARGS.
May be the support is removed?? @budtmo
I was able to launch emulator successfully using the below compose file.
version: '3'
services:
android-container:
image: budtmo/docker-android:emulator_11.0
deploy:
resources:
limits:
cpus: '8'
memory: 10000M
reservations:
cpus: '8'
memory: 10000M
privileged: true
ports:
- 4723:4723
- 5555:5555
- 9000
- 6080:6080
volumes:
- ./video-samsung_11.0:/tmp/video
environment:
- EMULATOR_DEVICE=Samsung Galaxy S10
- APPIUM=true
- WEB_VNC=true
- WEB_LOG=true
- WEB_LOG_PORT=9000
devices:
- "/dev/kvm"
Also I was not able to access logs using 9000 port.
Same problem here, still I have no solution.
Had the same issue. You can't have double quotes around the command, or they will be inserted in as well.
So in your compose file, just have for example:
EMULATOR_ADDITIONAL_ARGS=-gpu swiftshader_indirect -memory 8192 -netspeed full -accel on
Operating System
Ubuntu
Docker Image
budtmo/docker-android:emulator_13.0
Expected behaviour
The emulator should be launched successfully
Actual behaviour
The emulator is stuck at BOOTING status
Logs
When I start the emulator via docker-compose file, the emulator is never displayed. Just the background.
When I manually start the emulator it works fine.