-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
healthCheck not working #1580
Comments
Sounds indeed like a bug. Could you look into the generated Dockerfile, i.e.
|
Yes, that's the outcome of the docker:build but can you actually run docker:start with success? |
You are right, the samples are broken. The samples have probably only been created to check whether the images are probably built, not running. E.g. in busybox, no HTTP server is running, so the check with curl will always fail. Also, the timing parameters are not well chosen. I.e., a The section has a default timeout of 10 seconds, too short for a default healthcheck to kick in. So, for now you have several options:
But as mentioned, there are issues and possibilities to improve:
|
I encounter the same issue "No HEALTHCHECK configured". The proposed options did not make it work for me. I cannot even get the linked samples to compile using
|
Description
When both healthcheck and wait/healthy are configured, I get this error:
“Can not wait for healthstate of [busybox:latest] "healthybox1". No HEALTHCHECK configured.”
I don't include code snippets because this happens even if I run the official sample project (linked below).
If I only have a healthCheck section defined, without wait/healthy then the container starts but the healthcheck is missing so the error seems to indicate the true issue correctly - somehow the healthcheck is not created from the definition.
Info
mvn -v
) : 3.6.3The text was updated successfully, but these errors were encountered: