![Running a remote Docker Registry and getting 'HTTP response to HTTPS request' error on push – Kev's Development Toolbox Running a remote Docker Registry and getting 'HTTP response to HTTPS request' error on push – Kev's Development Toolbox](https://i0.wp.com/www.kevinhooke.com/wp-content/uploads/2017/09/img_59cdd5f6d797d.png?resize=380%2C525&ssl=1)
Running a remote Docker Registry and getting 'HTTP response to HTTPS request' error on push – Kev's Development Toolbox
![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)
Torizoncore-builder bundle with Insecure Registry: Error x509 Certificate signed by unknown authority - Technical Support - Toradex Community
![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/27208077-7aaaeda0-5211-11e7-9334-cdaa6bef3720.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/28021664/34140100-6df24eec-e446-11e7-8f07-6a8e8bee04fd.png)