Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:

When using atomic pull, the HTTP_PROXY and HTTPS_PROXY variables need to either be exported system wide, or provided in-line with the atomic pull command.

Version-Release number of selected component (if applicable):
AH-7.3.2

How reproducible:
Always

Steps to Reproduce:
1. Attempt to use a proxy to pull images
2.
3.

Actual results:
The pull will fail unless the variables are set as described since they are not sourced from /etc/sysconfig/docker since atomic pull uses skopeo.

If the vars are set in /etc/atomic.conf, they are still not used.

Expected results:
The proxy vars should be able to be set in /etc/atomic.conf, or some other config file that atomic will source.

Additional info:

Side note, not sure if this should be a separate bug, but if using a proxy and the system does not trust the proxy's CA, the pull will fail but will not indicate why.

I have created a PR for this upstream -> https://github.com/projectatomic/atomic/pull/964

If you can test it and provide feedback, that would be helpful.

And there is no any other environment variables are set in my RHEL7.2 system, it also doesn't work in upstream atomic, I also tried to export http_proxy environment by shell, atomic pull and push commands also can't receive the value of http_proxy.

[root@dhcp-2-50 atomic]# git rev-parse HEAD
2760e30296884e9160ff0b8e58c2e5d47791f01d

The syntax of the YAML format for this file is KEY : VALUE not KEY=VALUE.  Please alter your configuration file and try again.

(In reply to Brent Baude from comment #6)
> The syntax of the YAML format for this file is KEY : VALUE not KEY=VALUE. 
> Please alter your configuration file and try again.

thanks, it works well for me.

https://github.com/projectatomic/atomic/pull/1004

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1323