Closed mstorus closed 6 years ago
Ah, I wonder if @SvenDowideit can comment about why we're so specific with all the flags we turn on. I'm guessing it'd probably work to trim some of the ones we try to use (like --longmode
), since I run without several of them on my own machine without a problem (since I also run an older VirtualBox
).
The ones I specifically successfully have patched out on my local box (in virtualbox/machine.go
) are --longmode
, --triplefaultreset
, --vtxux
, and the newly added --portcount
(which was added for the speed increase it provides, so I'm sure there's something that could be done to intelligently detect whether it worked and silently ignore it if it didn't).
I'd hate to just start adding if vboxVersion > blahblahblah
checks all over the boot2docker-cli codebase, so I'm very interested in figuring out what our "minimal set" is (specifically for latest VirtualBox, but would also benefit older versions, obviously).
nope, those ones i have nothing for.
rather than doing vboxVersion
, call vboxmanage --help
, then parse and only use the options that are available. if you're missing some, just output a warning with vbox version and some distance from what we've tested metric.
easy
:snigger:
Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).
When I try to run
boot2docker -v init
it fails withVBoxManage: error: Unknown option: --longmode
Versions:
Unfortunately I can't run newer versions of VirtualBox because they cause my Mac to kernel panic.
Full output of
boot2docker -v init