Closed astayleraz closed 1 week ago
Hi, sorry for late reply. I've fixed the image healthcheck. Try to use version 9.0.1.
No it does not work yet and show a unhealthy status
9.0.1 is not working for me either.
@astayleraz Yes version 0.9.0 and 0.9.1 does not work because of healthy check I installed the version the 0.8.6 and it work fines.
Sorry for delay... I'm trying to find time to take a look on it.
When I inspect the unhealthy docker container, I see:
"Health": { "Status": "unhealthy", "FailingStreak": 365, "Log": [ { "Start": "2024-06-17T08:50:12.570369871-04:00", "End": "2024-06-17T08:50:12.592084642-04:00", "ExitCode": 1, "Output": " % Total % Received % Xferd Average Speed Time Time Time Current\n Dload Upload Total Spent Left Speed\n\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\ncurl: (7) Failed to connect to localhost port 443 after 0 ms: Couldn't connect to server\n" }, ... (several more of the same 443 failure)
Also, it's probably unrelated, but when I run this container using the docker compose in the readme, it does not work at all. I have to change the port mapping from 4011:80
to 4011:8080
.
From my finding the image does start with a service listening on Port 8080... .. while healthcheck tries https on port 443 and Dockerfile and Docs mention Port 80 und 443.
For me changing
healthcheck.test: curl --fail http://localhost:8080/health || exit 1
(not using https and port 8080) did help
@pniederlag thank you for your comment!
I'm moving all the endpoints to work with HTTPS because Chrome started to block HTTP. So I recommend to everybody to switch to HTTPS. It requires some more configuration to ignore certificate validation errors.
I can remove healthcheck at all and everybody will add by themselves if desired.
Closing due to inactivity
Our tests started to fail when we upgraded from v0.8.6 to v0.9.0. When we brought this up in docker, the status would go from health: starting to unhealthy soon after, and the logs did not show anything useful about what was failing.
We are unsure if we need to change something in our yml file with the upgrade. When we pin the version to 0.8.6 our tests and the instances work again. Here is the yml file we are using but now pinning to 0.8.6:
Let me know if there are more details that you might need or anything you want me to try.