![SOLVED] ERROR: Error response from daemon: Get https://myregistry:5000: http: server gave HTTP response to HTTPS client SOLVED] ERROR: Error response from daemon: Get https://myregistry:5000: http: server gave HTTP response to HTTPS client](https://www.yuribacciarini.com/content/images/2021/07/image7-ok-1.jpg)
SOLVED] ERROR: Error response from daemon: Get https://myregistry:5000: http: server gave HTTP response to HTTPS client
![Failed to pull image from Docker local insecure registry: http: server gave HTTP response to HTTPS client - Stack Overflow Failed to pull image from Docker local insecure registry: http: server gave HTTP response to HTTPS client - Stack Overflow](https://i.stack.imgur.com/y5bqe.png)
Failed to pull image from Docker local insecure registry: http: server gave HTTP response to HTTPS client - Stack Overflow
![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
![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/63787773-abb74180-c8f4-11e9-88be-91a41de4f7e3.png)
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 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
HTTP/Insecure repository: http: server gave HTTP response to HTTPS client · Issue #28321 · moby/moby · GitHub
![B! docker] 「server gave HTTP response to HTTPS client」と言われてDocker Private registoryのpushやpullができなかったときの対処 - Qiita B! docker] 「server gave HTTP response to HTTPS client」と言われてDocker Private registoryのpushやpullができなかったときの対処 - Qiita](https://qiita-user-contents.imgix.net/https%3A%2F%2Fcdn.qiita.com%2Fassets%2Fpublic%2Farticle-ogp-background-1150d8b18a7c15795b701a55ae908f94.png?ixlib=rb-4.0.0&w=1200&mark64=aHR0cHM6Ly9xaWl0YS11c2VyLWNvbnRlbnRzLmltZ2l4Lm5ldC9-dGV4dD9peGxpYj1yYi00LjAuMCZ3PTg0MCZoPTM4MCZ0eHQ2ND00NENNYzJWeWRtVnlJR2RoZG1VZ1NGUlVVQ0J5WlhOd2IyNXpaU0IwYnlCSVZGUlFVeUJqYkdsbGJuVGpnSTNqZ2Fqb3FJRGpnb19qZ296amdhWkViMk5yWlhJZ1VISnBkbUYwWlNCeVpXZHBjM1J2Y25uamdhNXdkWE5vNDRLRWNIVnNiT09Cak9PQnAtT0JqZU9CcXVPQmktT0JvLU9Cbi1PQnFPT0JqZUtBcGcmdHh0LWNvbG9yPSUyMzMzMyZ0eHQtZm9udD1IaXJhZ2lubyUyMFNhbnMlMjBXNiZ0eHQtc2l6ZT01NCZ0eHQtY2xpcD1lbGxpcHNpcyZ0eHQtYWxpZ249Y2VudGVyJTJDbWlkZGxlJnM9NTNkNGU4NjZkN2I0NzhmOGYxNjM1OTk4MmQyNGVhMTI&mark-align=center%2Cmiddle&blend64=aHR0cHM6Ly9xaWl0YS11c2VyLWNvbnRlbnRzLmltZ2l4Lm5ldC9-dGV4dD9peGxpYj1yYi00LjAuMCZ3PTg0MCZoPTUwMCZ0eHQ2ND1RRzVyYlhKNSZ0eHQtY29sb3I9JTIzMzMzJnR4dC1mb250PUhpcmFnaW5vJTIwU2FucyUyMFc2JnR4dC1zaXplPTQ1JnR4dC1hbGlnbj1yaWdodCUyQ2JvdHRvbSZzPTcyOTY1NDgyNjY4ODNlZWQ5Y2NkYjc4YmM3Y2M5OTgy&blend-align=center%2Cmiddle&blend-mode=normal&s=7a68ad50c7d3f09ccfd73f8c8a4a870d)