![Insecure-registry settings not recognized when using Windows Docker Daemon "...server gave HTTP response to HTTPS client" · Issue #802 · docker/for-win · GitHub Insecure-registry settings not recognized when using Windows Docker Daemon "...server gave HTTP response to HTTPS client" · Issue #802 · docker/for-win · GitHub](https://user-images.githubusercontent.com/28021664/34140100-6df24eec-e446-11e7-8f07-6a8e8bee04fd.png)
Insecure-registry settings not recognized when using Windows Docker Daemon "...server gave HTTP response to HTTPS client" · Issue #802 · docker/for-win · GitHub
![Insecure-registry settings not recognized when using Windows Docker Daemon "...server gave HTTP response to HTTPS client" · Issue #802 · docker/for-win · GitHub Insecure-registry settings not recognized when using Windows Docker Daemon "...server gave HTTP response to HTTPS client" · Issue #802 · docker/for-win · GitHub](https://user-images.githubusercontent.com/14967070/27232713-f049135c-526b-11e7-9466-c1edb4b9d024.png)
Insecure-registry settings not recognized when using Windows Docker Daemon "...server gave HTTP response to HTTPS client" · Issue #802 · docker/for-win · GitHub
![Private registry push fail: server gave HTTP response to HTTPS client · Issue #1874 · distribution/distribution · GitHub Private registry push fail: server gave HTTP response to HTTPS client · Issue #1874 · distribution/distribution · GitHub](https://user-images.githubusercontent.com/29914819/63787525-48c5aa80-c8f4-11e9-846b-6635b52cdbfc.png)
Private registry push fail: server gave HTTP response to HTTPS client · Issue #1874 · distribution/distribution · GitHub
![Torizoncore-builder bundle with Insecure Registry: Error x509 Certificate signed by unknown authority - Technical Support - Toradex Community Torizoncore-builder bundle with Insecure Registry: Error x509 Certificate signed by unknown authority - Technical Support - Toradex Community](https://europe1.discourse-cdn.com/toradexcommunity/original/2X/6/6f56e302257ef451c6078a86afade0f3f8e488e7.png)