Cannot download Docker images behind a proxy

Question

I installed Docker on my Ubuntu 13.10 (Saucy Salamander) and when I type in my console:

sudo docker pull busybox

I get the following error:

Pulling repository busybox
2014/04/16 09:37:07 Get https://index.docker.io/v1/repositories/busybox/images: dial tcp: lookup index.docker.io on 127.0.1.1:53: no answer from server

Docker version:

$ sudo docker version

Client version: 0.10.0
Client API version: 1.10
Go version (client): go1.2.1
Git commit (client): dc9c28f
Server version: 0.10.0
Server API version: 1.10
Git commit (server): dc9c28f
Go version (server): go1.2.1
Last stable version: 0.10.0

I am behind a proxy server with no authentication, and this is my /etc/apt/apt.conf file:

Acquire::http::proxy "http://192.168.1.1:3128/";
Acquire::https::proxy "https://192.168.1.1:3128/";
Acquire::ftp::proxy "ftp://192.168.1.1:3128/";
Acquire::socks::proxy "socks://192.168.1.1:3128/";

What am I doing wrong?

For the Windows users and boot2docker, see stackoverflow.com/a/29303930/6309 — VonC, Commented Mar 27, 2015 at 15:10
One minor detail: apt does not support SOCKS proxies at all. Acquire::socks::proxy means set the proxy for all URLs starting with a socks scheme. Since your sources.list does not have any socks:// URLs, that line is entirely ignored. — Hans-Christoph Steiner, Commented Dec 16, 2015 at 9:14

Thomas GL · Accepted Answer · 2021-08-11 13:03:40Z

972

Here is a link to the official Docker documentation for proxy HTTP: https://docs.docker.com/config/daemon/systemd/#httphttps-proxy

A quick outline:

First, create a systemd drop-in directory for the Docker service:

mkdir /etc/systemd/system/docker.service.d

Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY and HTTPS_PROXY environment variables:

[Service]
Environment="HTTP_PROXY=http://proxy.example.com:80/"
Environment="HTTPS_PROXY=http://proxy.example.com:80/"

If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable:

Environment="HTTP_PROXY=http://proxy.example.com:80/"
Environment="HTTPS_PROXY=http://proxy.example.com:80/"
Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com"

Flush changes:

$ sudo systemctl daemon-reload

Verify that the configuration has been loaded:

$ sudo systemctl show --property Environment docker
Environment=HTTP_PROXY=http://proxy.example.com:80/
Environment=HTTPS_PROXY=http://proxy.example.com:80/

Restart Docker:

$ sudo systemctl restart docker

Footnote regarding HTTP_PROXY vs. HTTPS_PROXY: for a long time, setting HTTP_PROXY alone has been good enough. But with version 20.10.8, Docker has moved on to Go 1.16, which changes the semantics of this variable: https://golang.org/doc/go1.16#net/http
For https:// URLs, the proxy is now determined by the HTTPS_PROXY variable, with no fallback on HTTP_PROXY.

edited Aug 11, 2021 at 13:03

Thomas GL

334 bronze badges

answered Jan 22, 2015 at 16:13

Alexandre Mélard

12.5k3 gold badges39 silver badges47 bronze badges

3

This works for Debian Jessie running Docker 1.6.2. Somehow editing /etc/default/docker does not work. Maybe I should remove export like the one documented for Centos.
– neurite
Commented Nov 5, 2015 at 19:29
2

For older SysV edit /etc/sysconfig/docker as in docs.oracle.com/cd/E37670_01/E37355/html/… - Oracle Linux 6.7
– SidJ
Commented Jan 7, 2016 at 3:26
4

NB: I assumed that 'daemon-reload' would suffice to apply changes to docker, but actually sudo systemctl restart docker is strictly required for it to work.
– Jose Alban
Commented Apr 6, 2016 at 8:56
5

For ubuntu 14.04 refer @n3o 's answer, Since systemctl is not available for ubuntu 14.04, it uses upstart to bring up the services.
– chinmay
Commented Sep 16, 2016 at 12:43
4

Now it is returning "Proxy Authentication Required"... how to config username and passoword?
– pinei
Commented Feb 24, 2017 at 15:00

| Show 20 more comments

Peter Mortensen · Accepted Answer · 2019-09-17 13:09:29Z

98

Your APT proxy settings are not related to Docker.

Docker uses the HTTP_PROXY environment variable, if present. For example:

sudo HTTP_PROXY=http://192.168.1.1:3128/ docker pull busybox

But instead, I suggest you have a look at your /etc/default/dockerconfiguration file: you should have a line to uncomment (and maybe adjust) to get your proxy settings applied automatically. Then restart the Docker server:

service docker restart

edited Sep 17, 2019 at 13:09

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Apr 16, 2014 at 19:22

mbarthelemy

12.8k4 gold badges42 silver badges43 bronze badges

9

In my case /etc/default/docker contained lowercased example (http_proxy), but to have things working I had to add uppercased setting (HTTP_PROXY) there.
– Mekk
Commented Mar 17, 2015 at 20:50
you shouldn't set the HTTP_PROXY for the docker client
– thomas.han
Commented Oct 5, 2015 at 5:50
3

Does not work with docker 1.9.1, instead see this answer below
– Peter Dotchev
Commented Dec 8, 2015 at 8:05
1

This works for Ubuntu 14.04 when installing docker from apt.dockerproject.org.
– Michael Kopp
Commented Jul 25, 2016 at 12:39
2

This does not work on Debian 8.8, and you need to set http_proxy in /etc/systemd/system/docker.service.d as shown in the accepted answer
– Roman Mik
Commented Jul 18, 2017 at 22:02

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 15:59:05Z

64

On CentOS the configuration file for Docker is at:

/etc/sysconfig/docker

Adding the below line helped me to get the Docker daemon working behind a proxy server:

HTTP_PROXY="http://<proxy_host>:<proxy_port>"
HTTPS_PROXY="http://<proxy_host>:<proxy_port>"

edited Sep 19, 2018 at 15:59

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Jun 18, 2014 at 5:31

Arun Y

93910 silver badges12 bronze badges

8

export HTTP_PROXY="http://<username>:<password>@<proxy_host>:<proxy_port>" for those behind corporate proxies
– Nicolas Mommaerts
Commented Jul 14, 2014 at 8:21
for me this worked ONLY without the export. Are you sure this is correct?
– frans
Commented Apr 13, 2015 at 7:28
4

For me export only works on CentOS6 and w/o on CentOS7
– user2363318
Commented Apr 23, 2015 at 17:12
1

On Centos7 I also had to not use export
– Banjocat
Commented May 13, 2015 at 19:04
2

export HTTP_PROXY=... is a Bashism, for non-Bash shells (such as what /bin/sh may be), use two lines HTTP_PROXY=... and then export HTTP_PROXY That said, I didn't need the export at all.
– Cameron Kerr
Commented Jul 29, 2015 at 13:33

| Show 2 more comments

Pablo · Accepted Answer · 2016-11-04 21:11:25Z

50

If you're using the new Docker for Mac (or Docker for Windows), just right-click the Docker tray icon and select Preferences (Windows: Settings), then go to Advanced, and under Proxies specify your proxy settings there. Click Apply and Restart and wait until Docker restarts.

edited Nov 4, 2016 at 21:11

Pablo

771 silver badge7 bronze badges

answered Jul 27, 2016 at 15:46

Pedro Madrid

1,9671 gold badge20 silver badges33 bronze badges

1

In case someone uses a locally-bound proxy (e.g. 127.0.0.1:8787) on macOS like me, here's the more detailed setup guide: Why a locally-bound proxy doesn't work
– Rockallite
Commented Jan 19, 2017 at 1:10
1

I have set my proxies via windows:settings but these proxies are not propagating to my containers stackoverflow.com/questions/48272933/…
– amique
Commented Jan 16, 2018 at 22:18
For me i needed only to put in my DNS Server and it worked then. Thanks.
– richin
Commented Apr 25, 2018 at 14:57
Oh thank you this was driving me insane.
– Justin Smith
Commented Jun 26, 2022 at 13:39

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 15:59:55Z

32

On Ubuntu you need to set the http_proxy for the Docker daemon, not the client process. This is done in /etc/default/docker (see here).

edited Sep 19, 2018 at 15:59

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Jul 11, 2014 at 9:10

gkephorus

1,31419 silver badges33 bronze badges

2

it says that I don't have permission to access your group. In the link.
– azizbro
Commented Oct 7, 2019 at 0:28
1

I don't think this works for Ubuntu 18.04 and above.
– zslim
Commented Feb 5, 2020 at 14:26

Add a comment |

Peter Mortensen · Accepted Answer · 2019-09-17 13:11:57Z

29

To extend Arun's answer, for this to work in CentOS 7, I had to remove the "export" commands. So edit

/etc/sysconfig/docker

And add:

HTTP_PROXY="http://<proxy_host>:<proxy_port>"
HTTPS_PROXY="https://<proxy_host>:<proxy_port>"
http_proxy="${HTTP_PROXY}"
https_proxy="${HTTPS_PROXY}"

Then restart Docker:

sudo service docker restart

The source is this blog post.

edited Sep 17, 2019 at 13:11

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Aug 21, 2014 at 11:00

zummed

2914 silver badges3 bronze badges

2

Only HTTP_PROXY is required (tested on Fedora 20).
– sheldonh
Commented Sep 23, 2014 at 21:17

Add a comment |

Community · Accepted Answer · 2020-06-20 09:12:55Z

Why a locally-bound proxy doesn't work

The Problem

If you're running a locally-bound proxy, e.g. listening on 127.0.0.1:8989, it WON'T WORK in Docker for Mac. From the Docker documentation:

I want to connect from a container to a service on the host

The Mac has a changing IP address (or none if you have no network access). Our current recommendation is to attach an unused IP to the lo0 interface on the Mac; for example: sudo ifconfig lo0 alias 10.200.10.1/24, and make sure that your service is listening on this address or 0.0.0.0 (ie not 127.0.0.1). Then containers can connect to this address.

The similar is for Docker server side. (To understand the server side and client side of Docker, try to run docker version.) And the server side runs on a virtualization layer which has its own localhost. Therefore, it won't connect to the proxy server on the localhost of the host OS.

The solution

So, if you're using a locally-bound proxy like me, basically you would have to do the following things to make it work with Docker for Mac:

Make your proxy server listen on 0.0.0.0 instead of 127.0.0.1. Caution: you'll need proper firewall configuration to prevent malicious access to it.
Add a loopback alias to the lo0 interface, e.g. 10.200.10.1/24:
```
 sudo ifconfig lo0 alias 10.200.10.1/24
```
Set HTTP and/or HTTPS proxy to 10.200.10.1:8989 from Preferences in Docker tray menu (assume that the proxy server is listening on port 8989).

After that, test the proxy settings by running a command in a new container from an image which is not downloaded:

$ docker rmi -f hello-world
  ...

$ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world

c04b14da8d14: Pull complete 
Digest: sha256:0256e8a36e2070f7bf2d0b0763dbabdd67798512411de4cdcf9431a1feb60fd9
Status: Downloaded newer image for hello-world:latest
  ...

Notice: the loopback alias set by ifconfig does not preserve after a reboot. To make it persistent is another topic. Please check this blog post in Japanese (Google Translate may help).

Thanks for this, I have been trying to find a solution for the last year or so with to get SquidMan on the Mac when trying to access both work and outside network through the company proxy. I got this to stick around by hooking it into launchd to be configured at startup. developer.apple.com/library/content/documentation/MacOSX/… — Proctor, Commented Jan 20, 2017 at 15:25
Thank's man. I finally found your post! It works. If you are using cntlm don't forget to add the binding 0.0.0.0 to your configuration. e.g. Listen 0.0.0.0: 8989 — Felix, Commented May 15, 2017 at 6:56

Peter Mortensen · Accepted Answer · 2018-09-19 16:10:23Z

13

This is the fix that worked for me: Ubuntu, Docker version: 1.6.2

In the file /etc/default/docker, add the line:

export http_proxy='http://<host>:<port>'

Restart Docker

sudo service docker restart

edited Sep 19, 2018 at 16:10

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Jul 12, 2016 at 12:16

n3o

2,8535 gold badges25 silver badges38 bronze badges

Working on Docker v1.12.1 on Ubuntu 14.04 and Mint 17.3
– wmarbut
Commented Aug 22, 2016 at 14:52
1

Works for 14.04.4 + Docker version 17.03.1-ce, build c6d412e
– petertc
Commented May 19, 2017 at 3:07

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 16:05:54Z

To configure Docker to work with a proxy you need to add the HTTPS_PROXY / HTTP_PROXY environment variable to the Docker sysconfig file (/etc/sysconfig/docker).

Depending on if you use init.d or the services tool you need to add the "export" statement (due to Debian Bug report logs - #767441. Examples in /etc/default/docker are misleading regarding the supported syntax):

HTTPS_PROXY="https://<user>:<password>@<proxy-host>:<proxy-port>"
HTTP_PROXY="https://<user>:<password>@<proxy-host>:<proxy-port>"
export HTTP_PROXY="https://<user>:<password>@<proxy-host>:<proxy-port>"
export HTTPS_PROXY="https://<user>:<password>@<proxy-host>:<proxy-port>"

The Docker repository (Docker Hub) only supports HTTPS. To get Docker working with SSL intercepting proxies you have to add the proxy root certificate to the systems trust store.

For CentOS, copy the file to /etc/pki/ca-trust/source/anchors/ and update the CA trust store and restart the Docker service.

If your proxy uses NTLMv2 authentication - you need to use intermediate proxies like Cntlm to bridge the authentication. This blog post explains it in detail.

Peter Mortensen · Accepted Answer · 2018-09-19 16:44:37Z

7

After installing Docker, do the following:

[mdesales@pppdc9prd1vq ~]$ sudo HTTP_PROXY=http://proxy02.ie.xyz.net:80 ./docker -d &
[2] 20880

Then, you can pull or do anything:

mdesales@pppdc9prd1vq ~]$ sudo docker pull base
2014/04/11 00:46:02 POST /v1.10/images/create?fromImage=base&tag=
[/var/lib/docker|aa088847] +job pull(base, )
Pulling repository base
b750fe79269d: Download complete
27cf78414709: Download complete
[/var/lib/docker|aa088847] -job pull(base, ) = OK (0)

edited Sep 19, 2018 at 16:44

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Jun 17, 2014 at 9:47

Marcello DeSales

22.1k14 gold badges82 silver badges80 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 16:08:37Z

6

In the new version of Docker, docker-engine, in a systemd based distribution, you should add the environment variable line to /lib/systemd/system/docker.service, as it is mentioned by others:

Environment="HTTP_PROXY=http://hostname_or_ip:port/"

edited Sep 19, 2018 at 16:08

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Dec 17, 2015 at 8:58

Mehdi Hamidi

1291 silver badge8 bronze badges

This was needed on RHEL7.
– dbalakirev
Commented Aug 23, 2016 at 14:32
2

add the line to the [Service] section
– volkit
Commented Feb 14, 2020 at 13:05

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 16:07:22Z

4

As I am not allowed to comment yet:

For CentOS 7 I needed to activate the EnvironmentFile within "docker.service" like it is described here: Control and configure Docker with systemd.

Edit: I am adding my solution as stated out by Nilesh. I needed to open "/etc/systemd/system/docker.service" and I had to add within the section

[Service]

EnvironmentFile=-/etc/sysconfig/docker

Only then was the file "etc/sysconfig/docker" loaded on my system.

edited Sep 19, 2018 at 16:07

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Sep 21, 2015 at 11:08

Maximilian Wollnik

3032 silver badges11 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 16:12:40Z

If using socks5 proxy, here is my test with Docker 17.03.1-ce with setting "all_proxy", and it worked:

# Set up socks5 proxy server
ssh sshUser@proxyServer -C -N -g -D \
     proxyServerIp:9999 \
     -o ExitOnForwardFailure=yes \
     -o ServerAliveInterval=60

# Configure dockerd and restart.
# NOTICE: using "all_proxy"
mkdir -p /etc/systemd/system/docker.service.d
cat > /etc/systemd/system/docker.service.d/http-proxy.conf <<EOF
[Service]
Environment="all_proxy=socks5://proxyServerIp:9999"
Environment="NO_PROXY=localhost,127.0.0.1,private.docker.registry.com"
EOF

systemctl daemon-reload
systemctl restart docker

# Test whether can pull images
docker run -it --rm alpine:3.5

Peter Mortensen · Accepted Answer · 2018-09-19 16:11:20Z

3

To solve the problem with curl in Docker build, I added the following inside the Dockerfile:

ENV http_proxy=http://infoprx2:8080
ENV https_proxy=http://infoprx2:8080
RUN apt-get update && apt-get install -y curl vim

Note that the ENV statement is BEFORE the RUN statement.

And in order to make the Docker daemon able to access the Internet (I use Kitematic with boot2docker), I added the following into /var/lib/boot2docker/profile:

export HTTP_PROXY=http://infoprx2:8080
export HTTPS_PROXY=http://infoprx2:8080

Then I restarted Docker with sudo /etc/init.d/docker restart.

edited Sep 19, 2018 at 16:11

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Oct 26, 2016 at 14:43

Bruno Negrão Zica

8042 gold badges8 silver badges16 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2019-09-17 13:16:37Z

3

The complete solution for Windows, to configure the proxy settings.

< user>:< password>@< proxy-host>:< proxy-port>

You can configure it directly by right-clicking on settings, in the Docker icon, and then Proxies.

There you can configure the proxy address, port, user name, and password.

In this format:

< user>:< password>@< proxy-host>:< proxy-port>

Example:

"geronimous:[email protected]:8080"

Nothing more than this.

edited Sep 17, 2019 at 13:16

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Aug 14, 2019 at 21:55

user2280949

773 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 16:06:42Z

2

If you are on Ubuntu, you should execute this command:

export https_proxy=http://your_name:password@ip_proxy:port docker

And reload Docker with:

service docker.io restart

Or go to /etc/docker.io with nano...

edited Sep 19, 2018 at 16:06

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Mar 3, 2015 at 15:23

koff75

991 silver badge12 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 16:39:56Z

2

If you're in Ubuntu, execute these commands to add your proxy.

sudo nano /etc/default/docker

And uncomment the lines that specifies

#export http_proxy = http://username:[email protected]:8050

And replace it with your appropriate proxy server and username.

Then restart Docker using:

service docker restart

Now you can run Docker commands behind proxy:

docker search ubuntu

edited Sep 19, 2018 at 16:39

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Mar 14, 2018 at 5:40

Gary Mendonca

2,0431 gold badge14 silver badges21 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2019-09-17 13:14:00Z

2

Perhaps you need to set up lowercase variables. In my case, my /etc/systemd/system/docker.service.d/http-proxy.conf file looks like this:

[Service]
Environment="ftp_proxy=http://<user>:<password>@<proxy_ip>:<proxy_port>/"
Environment="http_proxy=http://<user>:<password>@<proxy_ip>:<proxy_port>/"
Environment="https_proxy=http://<user>:<password>@<proxy_ip>:<proxy_port>/"

Good luck! :)

edited Sep 17, 2019 at 13:14

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Nov 10, 2017 at 12:51

Lawrence Ferreira

213 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2019-09-17 13:15:29Z

I was also facing the same issue behind a firewall. Follow the below steps:

$ sudo vim /etc/systemd/system/docker.service.d/http_proxy.conf
[Service]
Environment="HTTP_PROXY=http://username:password@IP:port/"

Don’t use or remove the https_prxoy.conf file.

Reload and restart your Docker container:

$ sudo systemctl daemon-reload
$ sudo systemctl restart docker
$ docker pull hello-world
Using default tag: latest
latest: Pulling from library/hello-world
1b930d010525: Pull complete
Digest: sha256:2557*********************************8
Status: Downloaded newer image for hello-world:latest

Peter Mortensen · Accepted Answer · 2018-09-19 16:08:05Z

1

Simply setting proxy environment variables did not help me in version 1.0.1... I had to update the /etc/default/docker.io file with the correct value for the "http_proxy" variable.

edited Sep 19, 2018 at 16:08

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Oct 18, 2015 at 1:53

Richil

1511 silver badge3 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 16:09:42Z

1

On Ubuntu 14.04 (Trusty Tahr) with Docker 1.9.1, I just uncommented the http_proxy line, updated the value and then restarted the Docker service.

export http_proxy="http://proxy.server.com:80"

and then

service docker restart

edited Sep 19, 2018 at 16:09

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Jan 26, 2016 at 0:53

Neo

4,7606 gold badges41 silver badges55 bronze badges

Add a comment |

nomad · Accepted Answer · 2020-04-11 15:14:22Z

1

This doesn't exactly answer the question, but might help, especially if you don't want to deal with service files.

In case you are the one is hosting the image, one way is to convert the image as a tar archive instead, using something like the following at the server.

docker save <image-name> --output <archive-name>.tar

Simply download the archive and turn it back into an image.

docker load <archive-name>.tar

answered Apr 11, 2020 at 15:14

nomad

5216 silver badges12 bronze badges

Add a comment |

shivam · Accepted Answer · 2021-07-12 16:34:35Z

1

Remove proxy from environment variables

unset http_proxy
unset https_proxy
unset no_proxy

and then restart your docker

answered Jul 12, 2021 at 16:34

shivam

4913 gold badges9 silver badges22 bronze badges

Add a comment |

vaughan · Accepted Answer · 2017-09-08 14:41:18Z

0

On RHEL6.6 only this works (note the use of export):

/etc/sysconfig/docker

export http_proxy="http://myproxy.example.com:8080"
export https_proxy="http://myproxy.example.com:8080"

NOTE: Both can use the http protocol.)

Thanks to https://crondev.com/running-docker-behind-proxy/

answered Sep 8, 2017 at 14:41

vaughan

7,2876 gold badges51 silver badges65 bronze badges

Add a comment |

Peter Mortensen · Accepted Answer · 2018-09-19 16:42:05Z

In my network, Ubuntu works behind a corporate ISA proxy server. And it requires authentication. I tried all the solutions mentioned above and nothing helped. What really helped was to write a proxy line in file /etc/systemd/system/docker.service.d/https-proxy.conf without a domain name.

Instead of

Environment="HTTP_PROXY=http://user@domain:password@proxy:8080"

or

Environment="HTTP_PROXY=http://domain\user:password@proxy:8080"

and some other replacement such as @ -> %40 or \ -> \\ I tried to use

Environment="HTTP_PROXY=http://user:password@proxy:8080"

And it works now.

Peter Mortensen · Accepted Answer · 2018-09-25 10:46:29Z

0

Try this:

sudo HTTP_PROXY=http://<IP address of proxy server:port> docker -d &

edited Sep 25, 2018 at 10:46

Peter Mortensen

31.4k22 gold badges109 silver badges132 bronze badges

answered Dec 22, 2015 at 11:25

Abdennour TOUMI

91.5k41 gold badges261 silver badges267 bronze badges

Add a comment |

The Godfather · Accepted Answer · 2021-06-08 10:07:57Z

Have resolved the issue by following the below steps:

step 1: sudo systemctl start docker

step 2: sudo systemctl enable docker
(Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.)

step 3: sudo systemctl status docker

step 4: sudo mkdir -p /etc/systemd/system/docker.service.d

step 5: sudo vi /etc/systemd/system/docker.service.d/proxy.conf

Set proxy as below

[Service]

Environment="HTTP_PROXY=http://proxy.server.com:80"

Environment="HTTPS_PROXY=http://proxy.server.com:80"

Environment="NO_PROXY=.proxy.server.com,*.proxy.server.com,localhost,127.0.0.1,::1"

step 6: sudo systemctl daemon-reload

step 7: sudo systemctl restart docker.service

step 8: vi /etc/environment and source /etc/environment

http_proxy=http://proxy.server.com:80
https_proxy=http://proxy.server.com:80
ftp_proxy=http://proxy.server.com:80
no_proxy=127.0.0.1,10.0.0.0/8,3.0.0.0/8,localhost,*.abc.com

Raisul · Accepted Answer · 2021-06-12 18:17:08Z

I had a problem like I needed to use proxy to use google's dns for project's dependency and for API request needed to communicate with a private server at the same time.

For RHEL7 I configured the system like this:

went to the directory /etc/sysconfig/docker

Environment=http_proxy="http://ip:port"
Environment=https_proxy="http://ip:port"
Environment=no_proxy="hostname"

then save the file and use the command :

sudo systemctl restart docker

after that configure your Dockerfile : setup the environment structure first:

ENV http_proxy http://ip:port
ENV https_proxy http://ip:port
ENV no_proxy "hostname"

that's all! :)

Collectives™ on Stack Overflow

Cannot download Docker images behind a proxy

28 Answers 28

Why a locally-bound proxy doesn't work

The Problem

I want to connect from a container to a service on the host

The solution

Have resolved the issue by following the below steps:

Not the answer you're looking for? Browse other questions tagged
proxy
docker
or ask your own question.

Linked

Hot Network Questions

Collectives™ on Stack Overflow

28 Answers 28

Why a locally-bound proxy doesn't work

The Problem

I want to connect from a container to a service on the host

The solution

Have resolved the issue by following the below steps:

Not the answer you're looking for? Browse other questions tagged proxydocker or ask your own question.

Linked

Related

Not the answer you're looking for? Browse other questions tagged
proxy
docker
or ask your own question.