Skip to content
This repository has been archived by the owner on Feb 27, 2018. It is now read-only.

Deprecate support for --dockerport flag. #153

Merged

Conversation

jonseymour
Copy link
Contributor

As the result of long standing issues with support for half-close of inbound
TCP connections to Virtual Box guests on (at least) OSX use of port-forwarded
docker connections should be discouraged.

So, if the user really wants to configure it, let them. Otherwise, don't
set it up in the first place.

See boot2docker issue #150 (and others) for details.

Docker-DCO-1.1-Signed-off-by: Jon Seymour jon.seymour@gmail.com (github: jonseymour)

@tianon
Copy link
Contributor

tianon commented Jun 17, 2014

Seems sane to me, but I defer this one strongly to @SvenDowideit who's played with it the most of the team AFAIK.

@SvenDowideit
Copy link
Contributor

I think its sane too, I just want a little thinking time and there are a few issues where vbox makes a mess of the host-only network atm - and one where b2d doesn't get the ip

@jonseymour
Copy link
Contributor Author

I just noticed that this pull request will prevent boot2docker ip working properly because the derivation of the ssh port currently assumes that "Forwarding(1)" always contains the ssh port. With this change, the ssh port will be listed as "Forwarding(0)". I'll submit a modified pull request that improves the robustness of the ssh port derivation so that it isn't position sensitive.

@SvenDowideit
Copy link
Contributor

I already made a PR for this yesterday :)

Please review

On 10 July 2014 05:59:00 GMT+10:00, jonseymour notifications@github.com wrote:

I just noticed that this pull request will prevent boot2docker ip
working properly because the derivation of the ssh port currently
assumes that "Forwarding(1)" always contains the ssh port. With this
change, the ssh port will be listed as "Forwarding(0)". I'll submit a
modified pull request that improves the robustness of the ssh port
derivation so that it isn't position sensitive.


Reply to this email directly or view it on GitHub:
#153 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

@SvenDowideit
Copy link
Contributor

ok - I'm planning on putting this into v.1.2.0 first week of August.

As the result of long standing issues with support for half-close of inbound
TCP connections to Virtual Box guests on (at least) OSX use of port-forwarded
docker connections should be discouraged.

So, if the user really wants to configure it, let them. Otherwise, don't
set it up in the first place.

See boot2docker issue boot2docker#150 (and others) for details.

Docker-DCO-1.1-Signed-off-by: Jon Seymour <jon.seymour@gmail.com> (github: jonseymour)
@jonseymour
Copy link
Contributor Author

Sven, I have reviewed #185 and seems sane. I've rebased this branch to remove the merge conflicts.

@SvenDowideit
Copy link
Contributor

very awesome :)

@SvenDowideit
Copy link
Contributor

LGTM

SvenDowideit pushed a commit that referenced this pull request Jul 31, 2014
Deprecate support for --dockerport flag.
@SvenDowideit SvenDowideit merged commit cb4be2b into boot2docker:master Jul 31, 2014
@jonseymour jonseymour deleted the 150-deprecate-dockerport-flag branch September 16, 2014 01:57
SvenDowideit added a commit to SvenDowideit/boot2docker-cli that referenced this pull request Nov 10, 2014
install & run ntpclient to make sure boot2docker's clock is set
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants