error during connect Get https://192.168.99.100:2376/v1.38/containers/json #2596

Foadsf · 2018-09-12T09:36:22Z

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

open terminal
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.

The text was updated successfully, but these errors were encountered:

Foadsf · 2018-09-12T10:25:25Z

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:

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:

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 · 2018-09-12T11:50:08Z

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

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

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

from here you may run docker-machine upgrade

these steps solved my problem for the moment.

Foadsf · 2018-09-25T14:11:14Z

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

YAMLcase · 2018-10-14T13:54:02Z

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 · 2018-11-17T19:11:21Z

@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-robott · 2019-02-15T02:00:29Z

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 · 2019-04-05T18:03:59Z

got same error :(

claudivanmoreira · 2019-04-13T18:24:40Z

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 · 2019-04-24T18:12:49Z

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 · 2019-05-24T06:34:47Z

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 · 2019-07-07T08:09:05Z

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

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

objectsecurity · 2019-07-18T20:46:05Z

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 · 2019-07-26T14:34:04Z

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 · 2019-09-07T21:06:48Z

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

PinakiKundu · 2019-09-13T19:01:02Z

<<<<<<< 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 ...

abmjunaed · 2019-10-14T09:40:03Z

Solved:
I updated from Docker toolbox to Docker for windows and this problem happened.
Then I deleted all the environment variables for windows starting with Docker.
It solved the problem

Rupinder1161 · 2020-01-04T09:07:20Z

just regenerate the machine and follow official docker documentation. worked for me
https://docs.docker.com/toolbox/faqs/troubleshoot/

tommyb82 · 2020-01-14T15:23:28Z

Likewise @abmjunaed - environment variables hanging around from previously (long) removed Docker Toolbox installation caused this problem with Docker Desktop (which was started ok after HyperV disable / reenable). Removed them all, restart terminal, all working great now 🚀

SteversIO · 2020-03-06T13:38:31Z

Just adding what worked for me:
I was upgrading from Window 10 Home && Docker Toolbox

to Windows 10 Pro && Docker for Windows.

These Environment Variables were used by Toolbox. They need deleted:

DOCKER_TLS_VERIFY
DOCKER_CERT_PATH
DOCKER_HOST
DOCKER_TOOLBOX_INSTALL_PATH

And then start a new terminal session so it doesn't pick them up.

Foadsf · 2020-03-17T15:48:51Z

One of the many reasons you should avoid Doker on Windows and use Docker Toolbox instead is the fact, that the former uses Hyper-V which only exists on Windows Pro and Enterprise:

although your hardware might support Hyper-V if you check the systeminfo command, it is impossible to activate on Windows Home editions. Hyper-V in my humble opinion is evil as it also locks any other virtualizations at boot time (more info here) and @#%# your Virtualbox. So do yourself a favor and avoid Docker on Windows and use Docker Toolbox instead. You may download the latest version of Docker Toolbox here

vakkisan · 2020-05-18T05:16:23Z

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

got this error in windows..

docker image ls
error during connect: Get https://192.168.99.100:2376/v1.40/images/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.

then restarted using docker-machine restart .. worked like a charm

docker-robott · 2020-07-01T03:13:21Z

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-robott added the version/Version 18.06.1-ce-win73 label Sep 12, 2018

This was referenced Sep 12, 2018

An error occurred trying to connect: Get https://192.168.xx.xx:2376/v1.18/containers/json: remote error: bad certificate docker/machine#673

Closed

Cannot run hello-world to confirm that the installation was successful #2364

Closed

docker-robott added the lifecycle/stale label Feb 15, 2019

docker-robott closed this as completed Mar 17, 2019

docker-robott added the lifecycle/locked label Jul 1, 2020

docker locked and limited conversation to collaborators Jul 1, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

error during connect Get https://192.168.99.100:2376/v1.38/containers/json #2596

error during connect Get https://192.168.99.100:2376/v1.38/containers/json #2596

Foadsf commented Sep 12, 2018 •

edited

Loading

Foadsf commented Sep 12, 2018 •

edited

Loading

Foadsf commented Sep 12, 2018

Foadsf commented Sep 25, 2018

YAMLcase commented Oct 14, 2018 •

edited

Loading

atifmir commented Nov 17, 2018 •

edited

Loading

docker-robott commented Feb 15, 2019

eugene-matvejev commented Apr 5, 2019

claudivanmoreira commented Apr 13, 2019 •

edited

Loading

shruti-rao commented Apr 24, 2019 •

edited

Loading

scarabetta commented May 24, 2019

marquish commented Jul 7, 2019

objectsecurity commented Jul 18, 2019 •

edited

Loading

halmai commented Jul 26, 2019

ChrisCWerner commented Sep 7, 2019

PinakiKundu commented Sep 13, 2019 •

edited

Loading

abmjunaed commented Oct 14, 2019

Rupinder1161 commented Jan 4, 2020

tommyb82 commented Jan 14, 2020

SteversIO commented Mar 6, 2020 •

edited

Loading

Foadsf commented Mar 17, 2020 •

edited

Loading

vakkisan commented May 18, 2020

docker-robott commented Jul 1, 2020

error during connect Get https://192.168.99.100:2376/v1.38/containers/json #2596

error during connect Get https://192.168.99.100:2376/v1.38/containers/json #2596

Comments

Foadsf commented Sep 12, 2018 • edited Loading

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

Foadsf commented Sep 12, 2018 • edited Loading

Foadsf commented Sep 12, 2018

Foadsf commented Sep 25, 2018

YAMLcase commented Oct 14, 2018 • edited Loading

atifmir commented Nov 17, 2018 • edited Loading

docker-robott commented Feb 15, 2019

eugene-matvejev commented Apr 5, 2019

claudivanmoreira commented Apr 13, 2019 • edited Loading

shruti-rao commented Apr 24, 2019 • edited Loading

scarabetta commented May 24, 2019

marquish commented Jul 7, 2019

objectsecurity commented Jul 18, 2019 • edited Loading

halmai commented Jul 26, 2019

ChrisCWerner commented Sep 7, 2019

PinakiKundu commented Sep 13, 2019 • edited Loading

abmjunaed commented Oct 14, 2019

Rupinder1161 commented Jan 4, 2020

tommyb82 commented Jan 14, 2020

SteversIO commented Mar 6, 2020 • edited Loading

Foadsf commented Mar 17, 2020 • edited Loading

vakkisan commented May 18, 2020

docker-robott commented Jul 1, 2020

Foadsf commented Sep 12, 2018 •

edited

Loading

Foadsf commented Sep 12, 2018 •

edited

Loading

YAMLcase commented Oct 14, 2018 •

edited

Loading

atifmir commented Nov 17, 2018 •

edited

Loading

claudivanmoreira commented Apr 13, 2019 •

edited

Loading

shruti-rao commented Apr 24, 2019 •

edited

Loading

objectsecurity commented Jul 18, 2019 •

edited

Loading

PinakiKundu commented Sep 13, 2019 •

edited

Loading

SteversIO commented Mar 6, 2020 •

edited

Loading

Foadsf commented Mar 17, 2020 •

edited

Loading