Closed chrsoo closed 5 years ago
One option you can use is a nexus server that would mirror the docker hub.
I did not know that Nexus 3 supports proxying Docker but it makes total sense, thanks for the tip! We are in the process of upgrading from Nexus 2 to Nexus 3 and it will now become a prerequisite for Docker adoption at my workplace unless support for NTLM proxies is implemented.
You’re better off having one anyway. That way you can have your own images hosted in-premise. Along with other benefits like Maven artifacts, site generation targets etc.
Sent from Mail for Windows 10
From: Christoffer SOOP Sent: September 12, 2017 4:08 AM To: docker/for-win Cc: Archimedes Trajano; Comment Subject: Re: [docker/for-win] Support for NTLM based proxies (#1064)
I did not know that Nexus 3 supports proxying Docker but it makes total sense, thanks for the tip! We are in the process of upgrading from Nexus 2 to Nexus 3 and it will now become a prerequisite for Docker adoption at my workplace unless support for NTLM proxies is implemented. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
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
/remove-lifecycle stale
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
/remove-lifecycle stale
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
/remove-lifecycle stale
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
Any news about the feature?
/remove-lifecycle stale
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
Expected behavior
Docker uses the Windows default credentials to access internet resources through a NTLM based proxy
Actual behavior
Docker times out with a message that it cannot access the requested resource, e.g.
Information
9C89F33A-AA87-4CBF-B00C-1A004A366034/2017-09-04_13-00-29
Steps to reproduce the behavior
Behind a NTLM proxy run any Docker command that requires network access, e.g.