Question 81265 in Docker Question posted in
The official documentation can be found here.

Get "https://registry-1.docker.io/v2/": proxyconnect tcp: dial tcp 192.168.65.1:3128

docker run -d –name=grafana -p 3000:3000 grafana/grafana-enterprise:9.2.0 Unable to find image ‘grafana/grafana-enterprise:9.2.0’ locally docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": proxyconnect tcp: dial tcp 192.168.65.1:3128: connect: connection refused.

How to solve this? https://registry-1.docker.io/v2/ the image when tried to access from browser

enter image description here

I was trying to implement Grafana in Docker by following this.

Tags:

2

Answers


  1. 0

    It is likely you have an internal proxy you need to connect through. You may be able to solve it using the HTTP PROXY instructions for docker: https://docs.docker.com/network/proxy/

    Login or Signup to reply.
  2. 0

    After you provided the image I can saw that your corporate proxy is requesting authentication. So, your docker is stopping on this connection step.

    Ps.: Proxies are different, so it’s important to check with your OPS team which kind of authentication your proxy expects.
    Anyways, try those steps separately testing again after each one

    1. Configure HTTP(S)_PROXY env variables

    Configure HTTP_PROXY and/or HTTPS_PROXY env variables in your WSL like that:

    http_proxy=http://username:password@hostname:port
export $http_proxy

    and/or

    https_proxy=http://username:password@hostname:port
export $https_proxy

    Where username and password are to authenticate in proxy and hostname and port are proxy DNS name/IP and (probably) port 3128 as I noticed in your logs

    1. Configure Docker desktop proxy https://docs.docker.com/network/proxy/

    2. In case your proxy is requiring NTLM authentication, you might have more issues. I would say you will need to try something like that > https://askubuntu.com/questions/1121521/how-to-configure-http-proxy-with-authentication-on-ubuntu-wsl-on-windows-10

    Workaround: Before doing any suggested steps, you can try to pull the docker image using private internet access such as a 4G or your home wifi. It will isolate your problem from the proxy thing

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search