You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this has been a long-standing issue, I'm happy to provide any other details as needed. I can move back up to 4.8.1 to do any testing you might need, but for now I've got to stick with 4.6.0 so I can get work done.
Thanks for the feedback. It's sad that you had to rollback to an older version. And thanks for your offer to help testing, this will help our team.
With 4.8 we improved reading the OS level proxy settings and we plan to deprecate the manual proxy settings in the future.
I'd like to get in touch with you to understand how you use proxies, why you need manual proxy settings. We can discuss here or in our roadmap ticket docker/roadmap#339 or a DM in our community Slack. Thank you.
Having the same issue and had to downgrade to 4.7.1 for it to work. Happy to help also Stefan if you need another guinea pig. thanks for looking into this.
Hi @dandrzejewski, thanks for submitting this issue! I think we've identified the problem, could you test this build and let me know if the issue is resolved? @glindsay78 same for you :)
With 4.8 we improved reading the OS level proxy settings and we plan to deprecate the manual proxy settings in the future.
This is great news. Please do this in a way that you actually realize, when the proxy settings change. We for example (and I guess we are not the only ones) have regularlary changing proxy settings via the day, whenever we connect to customer VPNs which enforce different proxy settings via auto-detection.
Browsers for example handle this very nicely after a few seconds of beeing connected to the new network and having new proxy settings.
Hi @dandrzejewski, thanks for submitting this issue! I think we've identified the problem, could you test this build and let me know if the issue is resolved? @glindsay78 same for you :)
@dandrzejewski Thanks for raising this. Indeed, we encountered an issue that the extensions marketplace isn't reachable behind a proxy at the moment. The team is working on it.
Activity
dandrzejewski commentedon May 10, 2022
Since this has been a long-standing issue, I'm happy to provide any other details as needed. I can move back up to 4.8.1 to do any testing you might need, but for now I've got to stick with 4.6.0 so I can get work done.
StefanScherer commentedon May 11, 2022
Thanks for the feedback. It's sad that you had to rollback to an older version. And thanks for your offer to help testing, this will help our team.
With 4.8 we improved reading the OS level proxy settings and we plan to deprecate the manual proxy settings in the future.
I'd like to get in touch with you to understand how you use proxies, why you need manual proxy settings. We can discuss here or in our roadmap ticket docker/roadmap#339 or a DM in our community Slack. Thank you.
glindsay78 commentedon May 11, 2022
Having the same issue and had to downgrade to 4.7.1 for it to work. Happy to help also Stefan if you need another guinea pig. thanks for looking into this.
laurazard commentedon May 11, 2022
Hi @dandrzejewski, thanks for submitting this issue! I think we've identified the problem, could you test this build and let me know if the issue is resolved? @glindsay78 same for you :)
Thanks!
paulchambers commentedon May 11, 2022
Same issue here and the test build has resolved it and is honoring the manual proxy settings again.
4.7.1 and 4.9.0 both working as expected. 4.8.1 broken.
pfeigl commentedon May 11, 2022
This is great news. Please do this in a way that you actually realize, when the proxy settings change. We for example (and I guess we are not the only ones) have regularlary changing proxy settings via the day, whenever we connect to customer VPNs which enforce different proxy settings via auto-detection.
Browsers for example handle this very nicely after a few seconds of beeing connected to the new network and having new proxy settings.
dandrzejewski commentedon May 11, 2022
I would caution against this, some of us work in complex proxy environments and it may be necessary to manually set proxies at various times.
I'll test the provided build shortly and provide feedback - thanks for the quick response to this!
laurazard commentedon May 11, 2022
Thanks for the feedback @dandrzejewski. If you care, there's a roadmap item here where you can leave further feedback that we are looking at.
dandrzejewski commentedon May 11, 2022
Everything seems to be working except the extensions marketplace - that does not appear to load.
glindsay78 commentedon May 11, 2022
Yes this build is working for me. Thanks!
StefanScherer commentedon May 12, 2022
@dandrzejewski Thanks for raising this. Indeed, we encountered an issue that the extensions marketplace isn't reachable behind a proxy at the moment. The team is working on it.
awynnejo commentedon May 18, 2022
Same issue here, 4.8.1 broken but 4.9.0 has resolved it.
mat007 commentedon May 18, 2022
Hi, we have just released Docker Desktop 4.8.2 with a fix. Thanks!
docker-robott commentedon Jun 17, 2022
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