Ensure udhcpc is not running for statically defined eth1 interface. #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
added a commit
that referenced
this pull request
Apr 29, 2014
Ensure udhcpc is not running for statically defined eth1 interface.
|
It comes down to the following order:
|
This was referenced Apr 29, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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