[RTFACT-8446] Docker token HTTP client does not inherit proxy (and other) settings of the remote repo Created: 23/Oct/15 Updated: 14/Nov/17 Resolved: 30/Dec/15
|Project:||Artifactory Binary Repository|
|Reporter:||Uriah Levy||Assignee:||Shay Yaakov (Inactive)|
The HTTP client we initialize for the token requests for a remote docker repo is not bound to any repo context. For situations where a proxy has to be defined for outbound requests, having to check the global proxy setting as system default is an ugly workaround.
Those requests should be bound to the remote repo settings (proxy, timeout settings, etc).
|Comment by Olivier Lambert [ 03/Nov/15 ]|
I think there is another problem.
By setting the system default proxy, the manifest files are downloaded from duckerhub and are put in the cache.
Is there another configuration used for downloading images ?
|Comment by Justin Georgeson [ 03/Nov/15 ]|
The images are being cached for me using the system default proxy workaround, but this defect came from a support ticket I submitted.
|Comment by Alix Lourme [ 16/Dec/15 ]|
Same issue for me, on Artifactory v4.3.2, a docker remote repository (on “Docker Hub”) seems not use the proxy configured in advanced tab for the "sub requests".
Consider a simple docker configuration : docker-local & docker-remote (behing company proxy) & docker-virtual (entry point).
This scenario works and validate the installation (internet proxy configured for docker deamon, for this sample … the objective is to use Artifactory as proxy)
But trying using Artifactory as registry proxy for official images:
In Artifactory log :
: Configuring the proxy as “System Default” solve the problem, but has some impacts on company domain requests (“no hosts” can’t be configured on the proxy).