Skip to content
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

Closed
2 tasks done
aniono opened this issue Dec 6, 2018 · 8 comments
Closed
2 tasks done

Comments

@aniono
Copy link

aniono commented Dec 6, 2018

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: 14ED1AE6-ABBA-40D5-956D-6A14593B64B5/20181206083212

Expected behavior

Actual behavior

Information

  • Windows Version: Windows 10 Pro 1803(17134.407)
  • Docker for Windows Version: Docker version 18.09.0, build 4d60db4

Steps to reproduce the behavior

  1. docker run hello-world
  2. C:\Program Files\Docker\Docker\Resources\bin\docker.exe: error during connect: Post https://192.168.99.100:2376/v1.39/containers/create: dial tcp 192.168.99.100:2376: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
@aniono aniono changed the title 14ED1AE6-ABBA-40D5-956D-6A14593B64B5/20181206083212 error during connect: Post https://192.168.99.100:2376/v1.39/containers/create: Dec 6, 2018
@rexnfx
Copy link

rexnfx commented Dec 17, 2018

I'm having the same problem. I recently updated docker versions. I'm also running bridged network adapter.

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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.
/lifecycle stale

@vpnicholls
Copy link

/remove-lifecycle stale

@mat007
Copy link
Member

mat007 commented Feb 7, 2020

Do you have a DOCKER_HOST environment variable?
If so, remove it and try again.

@vpnicholls
Copy link

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 docker run hello-world and now get a similar message with a localhost IP address:

C:\Program Files\Docker\Docker\resources\bin\docker.exe: error during connect: Post https://127.0.0.1:2376/v1.40/containers/create: dial tcp 127.0.0.1:2376: connectex: No connection could be made because the target machine actively refused it.

If I run docker version I get:

Client: Docker Engine - Community
Version: 19.03.5
API version: 1.40
Go version: go1.12.12
Git commit: 633a0ea
Built: Wed Nov 13 07:22:37 2019
OS/Arch: windows/amd64
Experimental: false
error during connect: Get https://127.0.0.1:2376/v1.40/version: dial tcp 127.0.0.1:2376: connectex: No connection could be made because the target machine actively refused it.

So I figure I've got to get the correct IP address and then add it somewhere?

@vpnicholls
Copy link

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:

Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:37 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.24)
  Go version:       go1.12.12
  Git commit:       633a0ea
  Built:            Wed Nov 13 07:36:50 2019
  OS/Arch:          windows/amd64
  Experimental:     false

@ghost
Copy link

ghost commented Mar 1, 2020

Open the port (2375) on the firewall. Worked for me.

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

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.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants