New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃殌 Feature Request ]: Document how to persist user data #410
Comments
take a look: #395 (comment) |
I offer a small PR, if you think it might help? Not sure how I didn't find #395 - I did search the issues before creating one, honest! Either way, I suggest we close this in favour of 395. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Idea
Document how to persist user data across restarts, OR, add volumes to the Dockerfile so this is the default behaviour
Probelm to solve
I spent a long time trying to understand how to make my installed app persist across restarts. Each time I got a brand new virtual android device.
When I mounted
/home/androidusr/emulator
, the device got stuck on BOOTING and there was no display in VNC.avdmanager list avd
showed no AVDs.It is necessary to mount
/home/androidusr/emulator
and also/home/.android/avd
. Then everything works as expected.I would like to add a section to the README, like:
to persist user data, mount these volumes:
I'll also include some detail about UID 1300.
Alternatively, we could add VOLUME declarations to the Dockerfile. But that would change the default behaviour. I think that persistence is the expected behaviour, though?
Additional Note
No response
The text was updated successfully, but these errors were encountered: