You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know, this fit neither "feature request" nor "bug", but no other template matches. Sorry about that.
We would like to run multiple test suites after another that requires different timezones.
It seems that cleanly changing the emulator timezone requires to recreate the whole container.
What we tried
Start a container without immediately starting the supervisor processes:
docker run --rm -it -e TZ=Europe/Berlin -e EMULATOR_DEVICE="Samsung Galaxy S10" -e WEB_VNC=true --device /dev/kvm -p 0.0.0.0:6081:6080 --entrypoint /bin/sh budtmo2/docker-android-pro:emulator_13.0_v2.11.1-p0 -c "trap \"exit\" TERM; while true; do sleep 1; done"
Inside the container, trigger the original ENTRYPOINT script after changing EMULATOR_ADDITIONAL_ARGS to our timezone needs.
Idea
I know, this fit neither "feature request" nor "bug", but no other template matches. Sorry about that.
We would like to run multiple test suites after another that requires different timezones.
It seems that cleanly changing the emulator timezone requires to recreate the whole container.
What we tried
EMULATOR_ADDITIONAL_ARGS='-timezone Europe/Kyiv' /home/androidusr/docker-android/mixins/scripts/run.sh
Anyway, when stopping the ENTRYPOINT script, some zombie processes are left.
Probelm to solve
Is there a clean way to switch timezones - without recreating the container? Hope, this is not as confusing as I feel right now. 🙂
Additional Note
No response
The text was updated successfully, but these errors were encountered: