You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The readme uses changedetection.io as the service name in the docker compose example. This causes a DNS resolution problem with the container's built-in example check for https://changedetection.io/CHANGELOG.txt. The container will resolve the hostname changedetection.io to the IP of the container rather than the desired external IP:
Is there an existing issue for this?
Current Behavior
The readme uses
changedetection.io
as the service name in the docker compose example. This causes a DNS resolution problem with the container's built-in example check forhttps://changedetection.io/CHANGELOG.txt
. The container will resolve the hostnamechangedetection.io
to the IP of the container rather than the desired external IP:Using the current docker compose example:
Checking the name resolution with ping inside the container you get the incorrect IP of the container itself:
This could lead user to think there is something wrong within the container or it's settings, when it's just a docker DNS problem.
This can be fixed by changing the default docker compose service name from
changedetection.io
tochangedetection
:After modification and checking name resolution in the container you get the correct external IP:
Expected Behavior
No response
Steps To Reproduce
see description
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: