#docker healthchecks
cobalt dust
It'll use the same interval, startPeriodIntervals that are configured in the docker image spec, but only use them until it gets a single healthy status, i.e. an exit code of 0.
once it's healthy, it'll consider the service to have been started.
so yes exactly a readiness check 🙂
If you want to get into the weeds, here's the commit that implements this: https://github.com/alexcb/dagger/commit/de059438ab783ffe3ad0a3b8472adda87b7e314e
it won't do anything like restart an unhealthy container.
mortal kernel
That looks exactly like what I was hoping for. Can't wait for it to land. Looks awesome