Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
http: server gave HTTP response to HTTPS client #2442
I tried the same get request in the browser using http instead of https and got this response
my /etc/docker/daemon.json is
I'm registering the existing remote docker daemon on my host using this command
When I run this command on my host machine, it was throwing this error
And the command "docker-machine ls" is giving
docker info :
Edit : I'm aware of this issue. But that didn't fix my issue.
I ran in to this same exact problem. However, I was able to get around it by using a fqdn versus the direct IP address. Here is what I have in /etc/docker/daemon.json:
We have a bunch of scripts to setup our docker environment and when we are calling docker pull, the above FQDN was getting resolved so docker pull looked like:
I updated the script to put the matching fqdn in and it worked.... not sure why docker cares, but it solved my problem...
The error in this case looks to be that the Docker API is running on non-TLS, but listening on port 2376 (which is the TLS port).
When setting up a machine with docker-machine, it'll generate and configure certificates to have a secure connection with the daemon (remote API); possibly you changed the daemon configuration and removed the part that configures TLS for the API
Please keep in mind that the GitHub issue tracker is not intended as a general support forum,
I'm closing this issue because this is not a bug, but feel free to continue the conversation