Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

Revert "Merge pull request #1552 from ehazlett/b2d-next" #1640

Merged
merged 1 commit into from
Aug 3, 2015

Conversation

nathanleclaire
Copy link
Contributor

This reverts commit 736ebb1, reversing
changes made to c6660bf.

Previously we were planning to move to a new Debian-based boot2docker, but it was decided at a high level that we were trying to do so too fast to do it properly for the 0.4.0 release. So, we are reverting this for now to revisit the issue for the next release, ideally with a proper migration path and strategy in place.

Signed-off-by: Nathan LeClaire nathan.leclaire@gmail.com

This reverts commit 736ebb1, reversing
changes made to c6660bf.

Signed-off-by: Nathan LeClaire <nathan.leclaire@gmail.com>
@ehazlett
Copy link
Contributor

ehazlett commented Aug 3, 2015

LGTM

nathanleclaire added a commit that referenced this pull request Aug 3, 2015
Revert "Merge pull request #1552 from ehazlett/b2d-next"
@nathanleclaire nathanleclaire merged commit af08468 into docker:master Aug 3, 2015
@nathanleclaire nathanleclaire deleted the revert_ngb2d branch August 3, 2015 22:20
@tianon
Copy link
Contributor

tianon commented Aug 3, 2015

👍

@sebgoa
Copy link
Contributor

sebgoa commented Oct 16, 2015

@ehazlett will the new b2d be used in the next release of machine ? is there a PR that brings this back ?

@nathanleclaire
Copy link
Contributor Author

@Runseb At some point, we will migrate over to a new OS for Machine (there have been some chronic issues with TCL), but due to the migration issues we are likely to encounter (custom b2d setups etc.) we're delaying it until we are very convinced it will be worth it to prioritize.

@sebgoa
Copy link
Contributor

sebgoa commented Oct 19, 2015

ok @nathanleclaire thanks, just curious as I have a b2d variant I would love to use with machine. need to test how to make it work with current vbox provider.

@nathanleclaire
Copy link
Contributor Author

@Runseb Cool in the meantime you can load custom ISOs with the --virtualbox-boot2docker-url flag (you might know that already, but they don't have to be boot2docker ISOs per se, just compatible with the same model), we are open as well to improving the VirtualBox driver as well to be more flexible, just haven't had time to work on it ourselves.

@sebgoa
Copy link
Contributor

sebgoa commented Oct 20, 2015

ok @nathanleclaire will try to have a look

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.

4 participants