proxyconnect tcp: dial tcp 127.0.0.1:1082:nnect: connection refused when pulling image

213 views
Skip to first unread message

Shijie Xu

unread,
Sep 21, 2024, 12:36:44 PM9/21/24
to kubernetes-sig-node
I'm in the process of setting up a local Ray cluster on my laptop by following the Ray Cluster quick start. However, I've encountered a problem: "proxyconnect tcp: dial tcp 127.0.0.1:1082:nnect: connection refused" when pulling docker images.

Here's some background information on my setup:
1. I'm using Kind to create a  local cluster.
2. http proxy is configured for containerd as i ma in china mainland.
``
(base) ➜  ~ cat /etc/systemd/system/containerd.service.d/http-proxy.conf
[Service]
Environment="HTTP_PROXY=http://localhost:1082"
Environment="HTTPS_PROXY=http://localhost:1082"
Environment="NO_PROXY=localhost, 127.0.0.0/8, ::1"
```
The proxy env variables are exported in the console according to Does cri support config proxy to support pull image via crictl and ctr, which works as expected.

> sudo ctr image pull docker.io/rayproject/ray:2.34.0 --hosts-dir=/etc/containerd/certs.d --debug

However, `helm install raycluster kuberay/ray-cluster --version 1.2.1` and `kubectl describe pod raycluster-kuberay-head-9fdtr` shows the connection to the proxy is refused.

My understanding is that kubectl relaies on crictl, to forwards the image pull request to containerd. Given that both crictl and ctr are able to successfully pull images, I'm puzzled as to why kubectl is still encountering issues.  And also the proxy is already proved by ctr/crictl, but still shows Could you provide some insight into this discrepancy?


Screenshot from 2024-09-21 19-35-49.png
Reply all
Reply to author
Forward
0 new messages