-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
Docker HEALTHCHECK
fails due to trying to access Martin at IPv6
#1674
Comments
Good point. martin/martin/src/srv/config.rs Line 6 in ba2e5d5
I don't know of better options than chaning it to this.
|
HEALTHCHECK
fails due to trying to access Martin at IPv6
Either that, or somehow rewrite the generated /etc/hosts at runtime and remove the localhost entry pointing to [::1], but just using 127.0.0.1 seems like a much simpler solution. |
This PR changes the docker-`HEALTHCHECK` only query ipv4 by default. Thanks @SmallhillCZ for the report ❤️ Resolves: #1674
Hi, with the new version we got a problem, where HEALTHCHECK instruction (introduced in #1397) fails due to trying to access Martin at IPv6 (localhost is translated to [::1]), while Martin is listening on IPv4 in the container.
Tried to run the healthcheck command inside the running container and found out the following:
This fails, makes the container status unhealthy and prevents the container to be recognized by our reverse proxy (Traefik), thus not being online:
This works okay:
/ # wget --spider http://127.0.0.1:3000/health Connecting to 127.0.0.1:3000 (127.0.0.1:3000) remote file exists
The text was updated successfully, but these errors were encountered: