Using a proxy while building images

Question

Using a proxy while building images

SebastianPfliegel opened this issue 7 years ago · 10 comments

Expected behavior

I need to use a proxy and I'm able to set it in the proxies tab in the Docker Settings. I expect Docker to use the set proxy for all kind of transactions: pulling/pushing images, in the final container and while building the actual image.

Actual behavior

Unfortunately this only applies to pulling/pushing images and the container. While building no proxy is set and therefore functions like apt-get and curl fail.

Information

Diagnostic ID: 80162FE0-1E80-4CAD-9437-195610F0B460/2017-12-04_15-43-59
Windows 10 Enterprise

Steps to reproduce the behavior

set a proxy in the settings GUI and apply
build a Dockerfile using RUN apt-get update
build fails due to connection refused

Workaround

As a workaround I'm able to set the build args myself. Here's a sample compose-file:

version: '2'
services:
  my_service:
    image: myservice:latest
    build:
      context: .
      dockerfile: Dockerfile
      args:
        - http_proxy=http://myproxy.com:8080
        - https_proxy=http://myproxy.com:8080
        - HTTP_PROXY=http://myproxy.com:8080
        - HTTPS_PROXY=http://myproxy.com:8080

Answer 1 · 2018-03-28T09:45:30.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Answer 2 · 2018-03-29T09:40:27.000Z

/remove-lifecycle stale

Answer 3 · 2018-06-03T05:08:19.000Z

I met same issue.
The workaround is work fine. Thanks! @SebastianPfliegel

Additionally, in my case, I found another solution.
I set proxy settings to ~/.docker/config.json . This issue was solved.
ref. https://docs.docker.com/network/proxy/

Environment

OS: Windows 10 Pro
Docker: Version 18.03.1-ce-win65 (17513)
Docker Compose: v1.21.1

Answer 4 · 2018-09-01T04:00:14.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Answer 5 · 2018-09-14T07:34:18.000Z

/remove-lifecycle stale

Answer 6 · 2018-12-13T02:00:32.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Answer 7 · 2018-12-17T10:46:30.000Z

/remove-lifecycle stale

So, apparently no-one cares :-)

Answer 8 · 2018-12-17T10:47:48.000Z

I guess so

Answer 9 · 2019-03-17T02:00:29.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Answer 10 · 2020-06-25T03:10:47.000Z

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked