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.

Sign up for GitHub

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

Jump to bottom

docker client cant connect to tcp://192.168.42.43:4243 #24

Closed
lalyos opened this issue Mar 12, 2014 · 2 comments · Fixed by #35
Closed

docker client cant connect to tcp://192.168.42.43:4243 #24

lalyos opened this issue Mar 12, 2014 · 2 comments · Fixed by #35

Comments

@lalyos
Copy link

lalyos commented Mar 12, 2014

Hi,

dvm starts up nicely, i can start containers etc. after a while I cant reach it from docker client:

2014/03/12 16:04:52 dial tcp 192.168.42.43:4243: operation timed out

I can still connect to docker by: dvm ssh, and containers are still running.

environment

  • osx: 10.9
  • dvm: 0.4.1
  • docker (client side): 0.8.1, build a1598d1
  • DOCKER_HOST=tcp://192.168.42.43:4243

diagnostic

by checking the open ports, i can see virtualbox listening

lsof -i|grep 4243
VBoxHeadl 11971 lalyos   20u  IPv4 0x459e391648321dc7      0t0  TCP *:4243 (LISTEN)
@cwjohnston
Copy link

It seems like the IP address assignment for eth1 changes after about ~20 minutes of uptime. I've seen this happen with both virtualbox and vmware_fusion providers.

fnichol added a commit that referenced this issue Apr 29, 2014
@fnichol
Ensure udhcpc is not running for statically defined eth1 interface.
7cd56c1 
This causes issues where the udhcpc process may eventually attempt to
acquire a new IP address from VitualBox or VMware's DHCP server, and
thus severing the connection to the Docker daemon (from the client's
point of view).

Sadly this is more of a Tiny Core Linux boot issue with the
busybox/udhcpc startup and not in boot2docker so it'll need to be
handled in Vagrant middleware.

Closes #28
Closes #24
Closes #8
@fnichol fnichol mentioned this issue Apr 29, 2014
Merged
@fnichol
Copy link
Owner

fnichol commented Apr 29, 2014

We've hopefully tracked this down and fixed in #35. Yay!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Ensure udhcpc is not running for statically defined eth1 interface. fnichol/dvm
3 participants
@cwjohnston @fnichol @lalyos