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 Get https://192.168.99.100:2376/v1.38/containers/json #2596

Closed
Foadsf opened this issue Sep 12, 2018 · 15 comments

Comments

@Foadsf
Copy link

commented Sep 12, 2018

  • I have tried with the latest version of my channel (Stable or Edge)

  • I have uploaded Diagnostics
    log.txt

  • Diagnostics ID: 4751922A-3186-4B60-BD14-950E40145369/20180912112345

Expected behavior

When running docker container ls to get a list of containers.

Actual behavior

getting the error message:

error during connect: Get https://192.168.99.100:2376/v1.38/containers/json: 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.

Information

  • Windows Version: Windows 10 Enterprise
  • Docker for Windows Version: Version 18.06.1-ce-win73 (19507), Channel: stable, b0f14f1

Steps to reproduce the behavior

  1. open terminal
  2. run docker container ls

P.S. Guys, I do appreciate your efforts. But I have never been able to touch docker without spending hours to fix errors and issues. I think the whole docker structure is getting too cluttered. You need to spend more time fixing the common errors and be active on website like StackOverflow answering the questions and issues.

@Foadsf

This comment has been minimized.

Copy link
Author

commented Sep 12, 2018

from here I ran the command in a admin cmd or powershell:

dism /Online /Disable-Feature:Microsoft-Hyper-V

now the the docker container ls works but upon running Docker for Windows I get the error:

docker for windows_2018-09-12_12-24-57

Hyper-V and Containers features are not enabled.
Do you want to enable them for Docker to be able to work properly?
Your computer will restart automatically.
Note: VirtualBox will no longer work.

and if I select cancel I get the error:
docker for windows_2018-09-12_12-26-22

An error occurred
Required feature(s) not enabled : Hyper-V and Containers.
Docker will exit.

This is exhausting!

P.S. you might also need to run the command bcdedit /set hypervisorlaunchtype off in an admin powershell/cmd

@Foadsf

This comment has been minimized.

Copy link
Author

commented Sep 12, 2018

upon restart the error happened again. the way I solved it this time:

  1. opened virtualbox and find the container where docker-machine or boot2docker (whatever it is!!!) is named default
  2. from here run docker-machine stop default and docker-machine start default
  3. at this step you might get the error:

Error response from daemon: client version ... is too new. Maximum supported API version is ...

  1. from here you may run docker-machine upgrade

these steps solved my problem for the moment.

@Foadsf

This comment has been minimized.

Copy link
Author

commented Sep 25, 2018

for those of you who end up here, do not install docker for windows. Install Docker ToolBox instead.

@yamlCase

This comment has been minimized.

Copy link

commented Oct 14, 2018

for those of you who end up here, do not install docker for windows. Install Docker ToolBox instead.

Hi @Foadsf, can you sum up why not to use Docker for Windows and instead ToolBox? I'm apparently uninformed. Thanks!

@atifmir

This comment has been minimized.

Copy link

commented Nov 17, 2018

@yamlCase Docker for windows is the best way to do it https://docs.docker.com/toolbox/toolbox_install_windows/ toolbox was for the legacy desktop.
Here is the solution that works, and there is no need to uninstall Oracle Virtual box hope this helps anyone else who experience this.
https://stackoverflow.com/questions/49679818/docker-could-not-read-ca-certificate

@docker-desktop-robot

This comment has been minimized.

Copy link
Collaborator

commented Feb 15, 2019

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

@eugene-matvejev

This comment has been minimized.

Copy link

commented Apr 5, 2019

got same error :(

@claudivanmoreira

This comment has been minimized.

Copy link

commented Apr 13, 2019

got same error using Docker For Windows:

error during connect: Get https://192.168.99.100:2376/v1.39/containers/json: 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.

OS Info:

Edition: Windows 10 Enterprise
Version: 1809
OS Build: 17763.437
Processor: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
System type: 64-bit

/lifecycle frozen

@shruti-rao

This comment has been minimized.

Copy link

commented Apr 24, 2019

Same error. /remove-lifecycle stale

$ docker version
Client:
Version: 18.03.0-ce
API version: 1.37
Go version: go1.9.4
Git commit: 0520e24302
Built: Fri Mar 23 08:31:36 2018
OS/Arch: windows/amd64
Experimental: false
Orchestrator: swarm
error during connect: Get https://192.168.99.100:2376/v1.37/version: dial tcp 19
2.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.

@scarabetta

This comment has been minimized.

Copy link

commented May 24, 2019

Same error here:

$ docker version
Client: Docker Engine - Community
Version: 18.09.2
API version: 1.39
Go version: go1.10.8
Git commit: 6247962
Built: Sun Feb 10 04:12:31 2019
OS/Arch: windows/amd64
Experimental: false
error during connect: Get https://192.168.99.100:2376/v1.39/version: 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.

@marquish

This comment has been minimized.

Copy link

commented Jul 7, 2019

would you check ?
eval $(docker-machine env default)

please post > docker-machine env default result if not solved.

@edward-objsec

This comment has been minimized.

Copy link

commented Jul 18, 2019

I am getting the same error, but only when shelling out from python (using subprocess.Popen) to execute docker commands. The ip in the error msg is as above: 192.168.99.100:2376. If I execute docker commands from a terminal they work as expected.

I have docker toolkit installed on a windows 10 machine. In the docker quickstart terminal the environment variable DOCKER_HOST=192.168.99.101:2376. I can ping 101, but pinging 100 errors with "TTL expired in transit."

Thanks in advance for your help.

@halmai

This comment has been minimized.

Copy link

commented Jul 26, 2019

I had the same error message after an unexpected power failure of the host computer.

After rebooting, I started VirtualBox and later on the Docker Toolbox. Then I get the same error message for the command docker images.

I deleted the virtual machine that the DockerTools installed for me and uninstalled the DockerTools too, then re-installed the same version. The problem was still the same.

Finally, I sent an ACPI shutdown to the VBox (Right click -> Close -> ACPI Shutdown) and exited from the Docker Toolbox too. Then, I did start only the Docker Toolbox and did not start the VBox. After a while, the Toolbox has started it automatically and it started to work fine.

I have no idea what exactly solved the problem but maybe it helps someone in the future.

@ChrisCWerner

This comment has been minimized.

Copy link

commented Sep 7, 2019

Got it working just by doing docker-machine restart on the Docker Toolbox.

@pinakispecial

This comment has been minimized.

Copy link

commented Sep 13, 2019

<<<<<<< SOLVED >>>>>>>

Got same error

docker: error during connect: Post https://192.168.99.100:2376/v1

and was banging my head as no help found over google. Then applied own intelligence and found the solution.

Looks like due to some issue your docker machine URL not got updated properly in environment file. So you need to fix that.


First Run : docker-machine ls
output will be like this [URL may be something else]:

NAME      ACTIVE   DRIVER   STATE     URL                        SWARM   DOCKER     ERRORS
default   -        hyperv   Running   tcp://192.168.1.194:2376           v18.09.9

If you are not able to see any VM then you have to create a VM using this link

I'm hoping you are able to see VM. now hit : set

Along a lot environment variable you will able to see DOCKER_HOST which will be ponting to wrong URL. For me it was like
DOCKER_HOST=tcp://192.168.1.194:2376

So simple change that set DOCKER_HOST=tcp://192.168.1.194:2376

Bingo!!!!

Just run docker run hello-world you should be able to see desire output ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.