docker-android
docker-android copied to clipboard
budtmo
unhealthy container
🐛 Bug Report
Operating System: Ubuntu 20.10
Docker Image: budtmo/docker-android-x86-8.1
Docker Version:
Docker version 20.10.6
Docker Command to start docker-android:
docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" -v /usr/local/backup/emulator1/.android:/root/.android -v /usr/local/backup/emulator1/android_emulator:/root/android_emulator --name emulator1 budtmo/docker-android-x86-8.1
Actual Behavior
After 2 or more runs Container shows unhealthy
I have the same issue. After 2 or more runs Container shows unhealthy and in noVNC doesn't appear the GUI of the emulator, only the DockerAndroid background. I've attached the log of the container.
Here I struggle with the same problem, the log also is equal to @sampaxk's, after executing docker run multiple times, the container goes unhealthy, docker system prune does not help, but restarting the whole system works (maybe restarting the Docker service itself work too, I haven't tried that yet)
I struggle too with this problem. budtmo/docker-android-x86-9.0 Sometimes it resolves without doing nothing. Today nothing seems to fix it and now I'm completly blocked :-( Restarting the docker service nor the machine solve the problem.
It seems that the problem depends on the content of the mounted volumes. In my case I'm mounting a jenkins workspace and cleaning it before the mount solve the problem.
It seems that the problem depends on the content of the mounted volumes. In my case I'm mounting a jenkins workspace and cleaning it before the mount solve the problem.
In my scenario there are no volumes at all.
I had the same issue, fixed it by firing the emulator process manually using this command
sudo docker exec -it -d container_id ./emulator/emulator -avd device_name
to know the device name exactly, you will need to run this command
sudo docker exec -it -d container_id ./emulator/emulator -list-avds
I remove the android cache file (cache.img only not the cache.img.qcow2) in /root/android_emulator inside the container before starting the container and it's always healthy now
