Repository navigation
docker.example.com is down, so docker compose doesn't work anymore #4221
Description
Description
Doing anything using docker compose on a clean server breaks because "docker.example.com" is down, and, unfortunately, it seems that docker compose does not work without that website (which is already bad).
error during connect: Get "http://docker.example.com/v1.24/version": command [ssh -l root -- ip docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=ssh: connect to host ip port 22: Connection refused
Steps To Reproduce
-Use the appropriate context to point to the machine
-Run "docker compose build"
Compose Version
Docker Compose version v2.17.2
Docker Environment
Docker version 23.0.4, build f480fb1
Anything else?
No response
Activity
crawlchange commentedon Apr 21, 2023
ndeloof commentedon Apr 21, 2023
This domain name is set by docker/cli as a default host name: https://github.com/docker/cli/blob/master/cli/connhelper/connhelper.go#L66
This is indeed source of confusion when the get eventually printed as an error message, and should be replaced by some more generic name, like
docker_host.@thaJeztah could you please transfert this issue to docker/cli, I don't have required privileges
thaJeztah commentedon Apr 21, 2023
I'd have to look up history, but I guess we used this one because "a" domain is needed for this (but "anything goes"). The
example.comwas probably used to prevent any possibility of hitting an actual domain (and maybelocalhostwas confusing for this feature, as it would be a remote server).Looking at https://www.rfc-editor.org/rfc/rfc2606.html#section-2
Perhaps something like
docker.localhostorapi.localhostcould still work (suggestions welcome!)crawlchange commentedon Apr 23, 2023
laurazard commentedon Apr 23, 2023
Right, thanks for the context!
The last part of that error is actually very relevant since it includes the ssh command that the CLI used to connect to the remote host and what the error returned by that command was (
ssh: connect to host ip port 22: Connection refused), which seems like it would be the most important for a user trying to debug an issue with their setup.The issue seems to be that the beginning is misleading, as we're not actually making an HTTP Get call to some random host, but I'm working on some of the remote connection/ssh stuff, I'll try to make the error handling a bit better :)