[🐛 Bug ]:the container does not start
Operating System
windows 10
Docker Image
Server: Docker Desktop 4.31.1, Version: 26.1.4;
Expected behaviour
Launching a docker-android
Actual behaviour
it does not start.Returns an error:Error response from daemon: error gathering device information while adding custom device "/dev/kvm": no such file or directory. Virtualization is enabled on the computer
Logs
docker run -d -p 6080:6080 -e EMULATOR_DEVICE="Samsung Galaxy S10" -e WEB_VNC=true --device /dev/kvm --name android-container budtmo/docker-android:emulator_11.0 Unable to find image 'budtmo/docker-android:emulator_11.0' locally emulator_11.0: Pulling from budtmo/docker-android 9ea8908f4765: Pull complete 78b654d3b11f: Pull complete 419c132e4fa0: Pull complete b87e9de57e9f: Pull complete 4f4fb700ef54: Pull complete d1e17f5d82a6: Pull complete 8ae847baa388: Pull complete 3c4d95f001a0: Pull complete 536c0aba7cc8: Pull complete 0618117649b4: Pull complete 81cd55dee3f1: Pull complete 6496f193897d: Pull complete 910e0c08613f: Pull complete 6c548e911796: Pull complete fcb33a1201a8: Pull complete d6c0a282c345: Pull complete bc7cf5a2bc67: Pull complete 598cd283dadf: Pull complete 17e35fbe72ef: Pull complete 98d296b07f33: Pull complete f5fc064d5506: Pull complete 772109b83c78: Pull complete cd64aac35be1: Pull complete 22a78cdf29b7: Pull complete b9ca373ceb30: Pull complete cb803ce2740d: Pull complete Digest: sha256:4bd3bc9ad6ed1fb77a979d245aa4a2c85591baf3d5dab744c55f3961743c1110 Status: Downloaded newer image for budtmo/docker-android:emulator_11.0 1d526d72818d7b20040e3cc5a4124a2ceaec12b0ec2c7236180ef12cb243d2e7 docker: Error response from daemon: error gathering device information while adding custom device "/dev/kvm": no such file or directory.
Do you have wsl 2 installed ?
Yes, wsl 2 installed.
You could try to run from the inside of WSL, I think the issue here is that on you windows host there is no path for kvm
You could try to run from the inside of WSL, I think the issue here is that on you windows host there is no path for kvm
It just failed for me in this manner on a fresh Ubuntu VM on aws
Sounds lika a "nested virtualization" problem to me. I do have a problem on Azure Pipelines with Azure workers. Those pipelines do not support nested virtualization therefore I need to pay for better machines, use 3rd party services or forget about automated test on CI/CD...
This tool works on macOS /systems? I can't run it on my Mac, I remove the /dev/kvm, but the emulator doesn't start.