docker pull private registry return 403 when set http_proxy to dfdaemon

[StephenLiuYa]

But when I remove http_proxy, docker pull is back to normal

[pouchrobot]

Thanks for your contribution. 🍻 @StephenLiuYa
While we thought ISSUE DESCRIPTION could be more specific, longer than 100 chars.
Here is a template at https://github.com/alibaba/pouch/blob/master/.github/ISSUE_TEMPLATE.md
Please edit this issue description instead of opening a new one.
More details, please refer to https://github.com/alibaba/pouch/blob/master/CONTRIBUTING.md

[fengzixu]

@StephenLiuYa Please supply information about the config of http_proxy at the comment.

[StephenLiuYa]

@fengzixu Environment="HTTP_PROXY=http://127.0.0.1:65001/"

[lggeor]

@fengzixu Environment="HTTP_PROXY=http://127.0.0.1:65001/"

解决了吗，我遇到同样的问题。求解!

[allencloud]

Please use the option --registry-mirrors instead of HTTP_PROXY in docker engine's config.

[allencloud]

First of all, thanks sincerely for constantly using and supporting Dragonfly. We will try our best to keep Dragonfly better, and keep community and eco-system growing.

To get more feedback of Dragonfly's adoption in industry, would you mind helping comment in issue dragonflyoss/dragonfly#219 to give more information about your enterprise's Dragonfly usage. Thanks a lot in advance. @StephenLiuYa