Official?

[efrecon]

Maybe this isn't the proper place to ask, but is there any particular reason the prototyping that has occurred within these images haven't made its way into the official images? HEALTHCHECK is an advertised feature of Dockerfiles and it feels that official images should show the way forward and demonstrate how to check upon themselves.

[tianon]

Yes, see docker-library/cassandra#76 (comment) (which we should add to the README here as well).

[efrecon]

Thanks for the reply. I found the thread that you are referring to a bit later. As future is kind of uncertain, I went for a solution that should provide all redis images at once, now and forward. I think that the idea should be applicable to most images, but with a different HEALTHCHECK that is. My hooks for build and push are more or less image independent. BTW, I blatantly stole your redis HEALTHCHECK code, hope this is ok.

[efrecon]

Would you accept PRs for these files (and dirs). I am slowly putting into place solutions that do not require bash (so they can run on top of Alpine as well) and can automatically be built. Migrating this might however need some changes to the various settings on the hub.

[efrecon]

ping?

[tianon]

Sorry for the delay.

BTW, I blatantly stole your redis HEALTHCHECK code, hope this is ok.

Absolutely, that's the whole point of this repository!

See docker-library/cassandra#76 (comment) -- this repository exists precisely as an example for users to set up their own HEALTHCHECKs which are relevant to their deployments. Many users are going to need modifications, etc, which is why I'd honestly not recommend users use these images directly, and why I'd be hesitant to do things like tag multiple versions which might encourage more users to do so.

[tianon]

See https://github.com/docker-library/faq#healthcheck for more detail about why these are intentionally separate.