statvfs('/root/android_emulator/snapshots/default_boot/ram.img') failed: No such file or directory

[lbbniu]

💬 Questions and Help

Please make sure that it is an issue / a feature request. If it is a question / help wanted, please visit our group chat. Thank you!

statvfs('/root/android_emulator/snapshots/default_boot/ram.img') failed: No such file or directory

[joshuabergeron]

I have also been seeing this error but don't really understand why, or what impact it has on the emulator session. It is definitely strange because the file exists and it is world readable.

[felipeloha]

+1

[svillegasc]

Hi, I have the same problem.

I don't know what have that I do. Inside the container in rute /root/android_emulator/snapshots/default_boot/ there is one file, ram.img.dirty.

Please help me.

[nucklehead]

I am seeing that error but only when i am not running with --privileged. Can you make sure you have that flag when running the docker command.

[reply2future]

I am seeing that error but only when i am not running with --privileged. Can you make sure you have that flag when running the docker command.

not work for me. I use docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S10" --name android-container budtmo/docker-android-x86-9.0 or docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" --name android-container budtmo/docker-android-x86-8.1

[reply2future]

I am seeing that error but only when i am not running with --privileged. Can you make sure you have that flag when running the docker command.

not work for me. I use docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S10" --name android-container budtmo/docker-android-x86-9.0 or docker run --privileged -d -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" --name android-container budtmo/docker-android-x86-8.1

It's actually about BIOS virtualization settings.And I enable this settings to resolve the problem.