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
{{ message }}
This repository was archived by the owner on Jan 20, 2026. It is now read-only.
I'm trying to run a custom system image (i.e. not from the list provided by emu-docker list) locally, but the state never changes from "connecting" and low level gRPC error: {"code":14,"message":"no healthy upstream"... gets displayed. Everything works fine with a system image from emu-docker list however (sys-img-android-28-P-x86_64.zip)
The steps I took:
Copied source.properties from sys-img-android-28-P-x86_64.zip to my custom system image since one was needed for step 2 (not exactly sure what this file is needed for)
emu-docker create emulator-30.0.17.zip <custom_sys_img_zip> (the system image is owned by the company where I work, so I unfortunately can't share it)
./create_web_container.sh followed by docker-compose -f js/docker/docker-compose.yaml up
Heya!
I'm trying to run a custom system image (i.e. not from the list provided by
emu-docker list) locally, but the state never changes from "connecting" andlow level gRPC error: {"code":14,"message":"no healthy upstream"...gets displayed. Everything works fine with a system image fromemu-docker listhowever (sys-img-android-28-P-x86_64.zip)The steps I took:
source.propertiesfromsys-img-android-28-P-x86_64.zipto my custom system image since one was needed for step 2 (not exactly sure what this file is needed for)emu-docker create emulator-30.0.17.zip <custom_sys_img_zip>(the system image is owned by the company where I work, so I unfortunately can't share it)./create_web_container.shfollowed bydocker-compose -f js/docker/docker-compose.yaml upAfter that this is what I see: