starred/docker-android

Fork 0

mirror of https://github.com/budtmo/docker-android.git synced 2026-04-25 12:15:52 +03:00

ram.img') failed: No such file or directory #124

New issue

Open

opened 2026-03-01 15:40:44 +03:00 by kerem · 6 comments

kerem commented

2026-03-01 15:40:44 +03:00

Owner

Originally created by @lbbniu on GitHub (Jul 11, 2019).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/175

💬 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

Originally created by @lbbniu on GitHub (Jul 11, 2019). Original GitHub issue: https://github.com/budtmo/docker-android/issues/175 ## 💬 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](https://gitter.im/budtmo/docker-android). Thank you!** statvfs('/root/android_emulator/snapshots/default_boot/ram.img') failed: No such file or directory

kerem commented

2026-03-01 15:40:44 +03:00

Author

Owner

@joshuabergeron commented on GitHub (Jul 12, 2019):

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.

@joshuabergeron commented on GitHub (Jul 12, 2019): 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.

kerem commented

2026-03-01 15:40:45 +03:00

Author

Owner

@felipeloha commented on GitHub (Nov 13, 2019):

@felipeloha commented on GitHub (Nov 13, 2019): +1

kerem commented

2026-03-01 15:40:45 +03:00

Author

Owner

@svillegasc commented on GitHub (Nov 22, 2019):

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.

@svillegasc commented on GitHub (Nov 22, 2019): 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.

kerem commented

2026-03-01 15:40:45 +03:00

Author

Owner

@nucklehead commented on GitHub (Dec 22, 2019):

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.

@nucklehead commented on GitHub (Dec 22, 2019): 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.

kerem commented

2026-03-01 15:40:45 +03:00

Author

Owner

@reply2future commented on GitHub (Apr 11, 2020):

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 commented on GitHub (Apr 11, 2020): > 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`

kerem commented

2026-03-01 15:40:45 +03:00

Author

Owner

@reply2future commented on GitHub (Apr 15, 2020):

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.

@reply2future commented on GitHub (Apr 15, 2020): > > 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.