-
Notifications
You must be signed in to change notification settings - Fork 76
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 fails after update to 2.20.0 #166
Comments
How to reproduce it? On my side: $ docker run --rm ghcr.io/tarampampam/error-pages:2.20.0
Unable to find image 'ghcr.io/tarampampam/error-pages:2.20.0' locally
2.20.0: Pulling from tarampampam/error-pages
8fa9176ffe45: Pull complete
4f4fb700ef54: Pull complete
Digest: sha256:47549faeaa41b225312b1bebb3e593f1a29ed02fcdbe175a4eb1e20ec7bd5e9b
Status: Downloaded newer image for ghcr.io/tarampampam/error-pages:2.20.0
{"level":"info","ts":1675193130.0279217,"msg":"We will use the requested template","name":"ghost"}
{"level":"info","ts":1675193130.0280774,"msg":"Server starting","addr":"0.0.0.0","port":8080,"default error page":"404","default HTTP response code":404,"proxy headers":[],"show request details":false,"localization disabled":false}
All seems ok |
Strange, i had restarted and also pulled the image to no avail. But after trying again, the healthcheck seems ok. Nevermind, i'll close the issue. |
Actually I got the same at Really nothing was chaged by me, just updated, what the additional info u need? |
How do you update, where, and what commands should I execute to reproduce the behavior? |
Get da latest container and recreate it. I dunno what I need to add more. And I as see this issue is not mine only. |
@SAOPP I mean how to reproduce it locally? Which commands I should run to see the failed health check? |
I don't have this info, cause I've updated my container and saw after several days that it unhealthy and error pages didn't work. It's all what I have homie. |
Maybe you have overridden the healcheck command somewhere? Without context and examples helping is very difficult |
|
Is there an existing issue for this?
Describe the bug
The container stays unhealthy because the healthcheck fails. This seems to be caused by the change
since the healthcheck is still
HEALTHCHECK &{["CMD" "/bin/error-pages" "--log-json" "healthcheck"] "7s" "2s" "0s" '\x00'}
Steps to reproduce
No response
Configuration files
No response
Relevant log output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: