![kubernetes - Failed to pull image from Docker local insecure registry: http: server gave HTTP response to HTTPS client - Stack Overflow kubernetes - 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)
kubernetes - Failed to pull image from Docker local insecure registry: http: server gave HTTP response to HTTPS client - Stack Overflow
![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
docker compose v2.6.0 build error "http: server gave HTTP response to HTTPS client" · Issue #9540 · docker/compose · GitHub
![server gave HTTP response to HTTPS client」と言われてDocker Private registoryのpushやpullができなかったときの対処 - Qiita 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-9f5428127621718a910c8b63951390ad.png?ixlib=rb-4.0.0&w=1200&mark64=aHR0cHM6Ly9xaWl0YS11c2VyLWNvbnRlbnRzLmltZ2l4Lm5ldC9-dGV4dD9peGxpYj1yYi00LjAuMCZ3PTkxNiZ0eHQ9JUUzJTgwJThDc2VydmVyJTIwZ2F2ZSUyMEhUVFAlMjByZXNwb25zZSUyMHRvJTIwSFRUUFMlMjBjbGllbnQlRTMlODAlOEQlRTMlODElQTglRTglQTglODAlRTMlODIlOEYlRTMlODIlOEMlRTMlODElQTZEb2NrZXIlMjBQcml2YXRlJTIwcmVnaXN0b3J5JUUzJTgxJUFFcHVzaCVFMyU4MiU4NHB1bGwlRTMlODElOEMlRTMlODElQTclRTMlODElOEQlRTMlODElQUElRTMlODElOEIlRTMlODElQTMlRTMlODElOUYlRTMlODElQTglRTMlODElOEQlRTIlODAlQTYmdHh0LWNvbG9yPSUyMzIxMjEyMSZ0eHQtZm9udD1IaXJhZ2lubyUyMFNhbnMlMjBXNiZ0eHQtc2l6ZT01NiZ0eHQtY2xpcD1lbGxpcHNpcyZ0eHQtYWxpZ249bGVmdCUyQ3RvcCZzPWJiZDM0OTJlMDVlZTZkYzRjOTMxYzUyNjg5YTA4NzZi&mark-x=142&mark-y=112&blend64=aHR0cHM6Ly9xaWl0YS11c2VyLWNvbnRlbnRzLmltZ2l4Lm5ldC9-dGV4dD9peGxpYj1yYi00LjAuMCZ3PTYxNiZ0eHQ9JTQwbmttcnkmdHh0LWNvbG9yPSUyMzIxMjEyMSZ0eHQtZm9udD1IaXJhZ2lubyUyMFNhbnMlMjBXNiZ0eHQtc2l6ZT0zNiZ0eHQtYWxpZ249bGVmdCUyQ3RvcCZzPThlNzczM2NmNmUxYWM1NGVmMWJhMjNmZmM4NmIxY2Y0&blend-x=142&blend-y=491&blend-mode=normal&s=29550a19a5c1a4342f4adc7d3f0d804f)
server gave HTTP response to HTTPS client」と言われてDocker Private registoryのpushやpullができなかったときの対処 - Qiita
http registry login (`http: server gave HTTP response to HTTPS client`) · Issue #887 · containerd/nerdctl · GitHub
![3.2.9 - failed to push tagged image to local registry, "server gave HTTP response to HTTPS client" — Linux Foundation Forums 3.2.9 - failed to push tagged image to local registry, "server gave HTTP response to HTTPS client" — Linux Foundation Forums](https://s.gravatar.com/avatar/9500fe751eb3aa7288a876d2655e5d30?s=480&r=pg&d=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fbf.png)
3.2.9 - failed to push tagged image to local registry, "server gave HTTP response to HTTPS client" — Linux Foundation Forums
![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)