Docker Community Forums

Share and learn in the Docker community.

Is COMPOSE_HTTP_TIMEOUT still used when DOCKER_HOST=ssh://dockerhost?

I’m having a problem where “docker-compose pull” sometimes reports errors like:

ERROR: for grafana  Get https://registry-1.docker.io/v2/grafana/grafana/manifests/sha256:4171e7e8c44bb17f9e5bffdcd3710a6d624828d73b4eb638682543c5ce86bbe9: proxyconnect tcp: dial tcp 192.168.65.1:3129: i/o timeout
Get https://registry-1.docker.io/v2/grafana/grafana/manifests/sha256:4171e7e8c44bb17f9e5bffdcd3710a6d624828d73b4eb638682543c5ce86bbe9: proxyconnect tcp: dial tcp 192.168.65.1:3129: i/o timeout

I don’t think it’s a network issue. At first I thought the Docker for Mac pre-set 192.168.65.1:3129 proxy was the problem and I commented in https://github.com/docker/for-mac/issues/2467#issuecomment-668177009 but now I think that’s a red herring.

I wonder if the problem is related to me switching to DOCKER_HOST=ssh://dockerhost recently. Previously I was using DOCKER_HOST=tcp://dockerhost:2376.

I’ve always had to use COMPOSE_HTTP_TIMEOUT=180 and maybe that env variable is not used for ssh connections?

WORKAROUND: it seems docker-compose pull --no-parallel avoids the timeout error I’m seeing with a DOCKER_HOST=ssh:// connection to my Docker for Mac.