search

docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.43k stars 117 forks source link

`Bypass proxy` option does not take effect. #5959

Closed mstratford-dt closed 2 years ago

mstratford-dt commented 3 years ago

Expected behavior

Setting Bypass proxy settings for these hosts & domains to a local domain that should not be transmitted via the proxy.

I should be able to run docker login <domain_in_no_proxy> and have it authenticate successfully.

Actual behavior

Setting Bypass proxy settings for these hosts & domains to a domain, ip address or range does not take affect using a proxy.

Running commands such as docker login <domain_in_no_proxy> fails with the following, since it is sending these requests via the proxy, which provides internet access only.

Authenticating with existing credentials...
Login did not succeed, error: Error response from daemon: Get https://<domain_in_no_proxy>/v2/: net/http: TLS handshake timeout`

Turning off the manual proxy entirely allows the local repository to be accessable, but breaks downloading images from internet repositories for us.

Information

These were tested on the basis of reports from other similar looking GitHub issues:

In doing so, I have also factory reset docker (with the "Settings Version too high" prompt when downgrading).

We use Cisco AnyConnect, which is specifically noted in the change logs for 3.4.0 with a switch of vpnkit: Here. As noted above, this change actually breaks our proxy support.

Steps to reproduce the behavior

  1. Use any of the affected versions listed above.
  2. Configure proxy for http and https in Docker for Mac. Set the proxy bypass to the domain of the local repository server
  3. docker login <domain_in_no_proxy> fails.
  4. Disable proxy settings in Docker for Mac
  5. docker login <domain_in_no_proxy> succeeds.
docker-robott commented 2 years ago

Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30 days 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

mstratford-dt commented 2 years ago

/remove-lifecycle stale

docker-robott commented 2 years ago

Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30 days 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

mstratford-dt commented 2 years ago

/remove-lifecycle stale

This is still a problem we are experiencing.

docker-robott commented 2 years ago

Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30 days 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

docker-robott commented 2 years ago

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