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
A “healthcheck” is a way in which a user can determine the “health” or readiness of the primary process running inside of a container. It is more than a simple “is my container running?” question. Think of it more like “is my application ready?” So, a healthcheck is really a way to verify that both the container and its applications are responsive.
As noted in opencontainers/umoci#352 (comment) when I asked for healthcheck support umoci maintainers noted me this is not an standard OCI feature, this is docker specific. So this brings up some considerations:
KIWI containers are all OCI images at build time only on the very last step they are converted from OCI to Docker format
Do we want to support non OCI features?
umoci can't be used to set the healthcheck as it implements the OCI standard
Buildah ignores healthcheck flags if they are used on non Docker images, which is the case in KIWI
So keeping the current implementation of container builds in KIWI it is not straight forward to include healthcheck support, as KIWI by design builds OCI images.
There could be a chance to implement support for it limited to buildah but this would require a relevant refactor. It is not clear to me the effort is worth.
Problem description
A “healthcheck” is a way in which a user can determine the “health” or readiness of the primary process running inside of a container. It is more than a simple “is my container running?” question. Think of it more like “is my application ready?” So, a healthcheck is really a way to verify that both the container and its applications are responsive.
For details see:
Expected behaviour
kiwi should be able to make use of the healtcheck feature
The text was updated successfully, but these errors were encountered: