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
Health check fails on v2.28.0 #3119
Comments
There is already a fix for that: #3087
Or whatever interface your container is listening to |
Hello, |
Any ETA on when the fix will be approved? We have 20+ filebrowser containers showing unhealthy. It's unsettling. X'D |
Since I sort of caused the bug (but fixing another bug/missing-feature), I will try to help, if you have docker build -t filebrowser/filebrowser:31119-fix https://github.com/CorySanin/filebrowser.git#bugfix/healthcheck and then use image name |
Description
The latest image (v2.28.0) of filebrowser from docker hub reports an unhealthy status even though there are no errors and the container is working as expected.
Expected behaviour
Container should report healthy
What is happening instead?
Container is reporting unhealthy
Additional context
Because the container is reporting unhealthy, errors are thrown and several other things fail. For example, a reverse proxy might think this service is unavailable and failover.
How to reproduce?
Docker compose:
See that the health check for the container is reported as unhealthy in portainer. There is no difference in logs and functionality. App is working perfectly as expected but still shows unhealthy.
The text was updated successfully, but these errors were encountered: