-
Notifications
You must be signed in to change notification settings - Fork 35
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
unhealthy status after upgrade from v0.8.6 to v0.9.0 #151
Comments
Hi, sorry for late reply. |
No it does not work yet and show a unhealthy status |
9.0.1 is not working for me either. |
@astayleraz |
Same here (kamilkisiela/graphql-hive#4414) |
Sorry for delay... |
When I inspect the unhealthy docker container, I see: 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 |
From my finding the image does start with a service listening on Port 8080... For me changing
|
@pniederlag thank you for your comment! I'm moving all the endpoints to work with HTTPS because Chrome started to block HTTP. I can remove healthcheck at all and everybody will add by themselves if desired. |
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.
The text was updated successfully, but these errors were encountered: