Closed gounthar closed 1 year ago
healthcheck:
test: [ "CMD", "/android/sdk/platform-tools/adb", " connect", "localhost:5555" ]
interval: 5s
timeout: 3s
retries: 10
start_period: 15s
Works fine for me.
@dduportal gave me a hint. docker inspect
gives me the information I was looking for:
"Healthcheck": {
"Test": [
"CMD-SHELL",
"/android/sdk/platform-tools/adb shell getprop dev.bootcomplete | grep \"1\""
],
"Interval": 30000000000,
"Timeout": 30000000000,
"StartPeriod": 30000000000,
"Retries": 3
},
Hi there,
First of all, thanks for this set of images, they are very useful to me. 🙏 I have a complex (to me) set of services defined in a
docker-compose.yml
file, and I havedepends-on
definition for services depending on the emulator.For the time being, I have hardcoded
sleep
time in temporary services because even ifdocker
says theemulator
service is up and running, the emulator hasn't finished booting for some time...I would like to get rid of the
sleep
and use ahealthcheck
command on the emulator container. Does theDockerfile
already defines ahealthcheck
? Is there anyhealthcheck
command you think of that could help me knowing when the emulator is ready? I thought of anadb
command but it's not part of the docker image.Thank you.