-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error during connect: Post https://192.168.99.100:2376/v1.39/containers/create: #3041
Comments
I'm having the same problem. I recently updated docker versions. I'm also running bridged network adapter. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
/remove-lifecycle stale |
Do you have a |
I checked and, yes, I did. It was referencing that IP address. I've removed the environment variable now and rebooted my laptop. I've tried
If I run Client: Docker Engine - Community So I figure I've got to get the correct IP address and then add it somewhere? |
So, it seems my issue was related to this issue: #741 Removing DOCKER_TLS_VERIFY from my environment variables and then setting "Expose daemon on tcp://localhost:2375" in Docker. Reboot, and the running docker version, I get:
|
Open the port (2375) on the firewall. Worked for me. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
Actual behavior
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: