RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1106334 - environment variable "https_proxy" does not work for docker pull
Summary: environment variable "https_proxy" does not work for docker pull
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: golang
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jakub Čajka
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-09 06:04 UTC by Guohua Ouyang
Modified: 2016-02-01 03:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-01 03:29:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Mimmus 2014-06-16 12:18:17 UTC 
Adding:

HTTP_PROXY=http://proxy.pitagora.it:3128/
HTTPS_PROXY=http://proxy.pitagora.it:3128/

to /etc/sysconfig/docker and restarting service, solves the problem.
Comment 3 Guohua Ouyang 2014-06-16 23:33:32 UTC 
(In reply to Mimmus from comment #2)
> Adding:
> 
> HTTP_PROXY=http://proxy.pitagora.it:3128/
> HTTPS_PROXY=http://proxy.pitagora.it:3128/
> 
> to /etc/sysconfig/docker and restarting service, solves the problem.

you add both http_proxy and https_proxy, as I said http_proxy works there, so no matter https_proxy is there or not.

if you only add https_proxy, does it work?
Comment 4 Daniel Walsh 2014-06-17 18:55:36 UTC 
Not sure https_proxy is supported by golang.  I don't see anything in docker to support either.  This support must be coming from a golang library.
Comment 5 Daniel Walsh 2014-06-17 18:56:54 UTC 
I am not sure if this is a bug or not.
Comment 6 Guohua Ouyang 2014-06-18 02:46:44 UTC 
(In reply to Daniel Walsh from comment #4)
> Not sure https_proxy is supported by golang.  I don't see anything in docker
> to support either.  This support must be coming from a golang library.

there is a golang issue "net/http: ProxyFromEnvironment doesn't support "https_proxy" environmental variables", 
and it's said it will to be fixed in go 1.3.
https://code.google.com/p/go/issues/detail?id=6181

I'd like to test it when go 1.3 is available to RHEL7.

If we're going to close the bug as NOTABUG, I think it's better to document the problem because end-user may still hit the issue, even it belongs to golang.
Comment 8 Guohua Ouyang 2014-09-17 07:51:59 UTC 
Checked with docker-1.2.0-14.el7.x86_64 and golang 1.3.1,
only set https_proxy=squid.corp.redhat.com:3128 still not work.
Comment 9 Daniel Walsh 2014-09-19 17:42:15 UTC 
Well I guess from reading the golang issue, it was never touched.
Note You need to log in before you can comment on or make changes to this bug.