search

fnichol / dvm

An on demand Docker virtual machine, thanks to Vagrant and boot2docker. Works great on Macs and other platforms that don't natively support the Docker daemon. Support VirtualBox, VMware, and Parallels.
http://fnichol.github.io/dvm
Apache License 2.0
458 stars 71 forks source link

Bump to latest 0.9.0 of boot2docker #38

Closed spheromak closed 10 years ago

spheromak commented 10 years ago

Issue running brew install docker will get you docker 0.11, and the current dvm boot2docker installs incompatable version of docker under the hood.

This is optimistic that @mitchellh will pull/rebuild mitchellh/boot2docker-vagrant-box#47

fnichol commented 10 years ago

Looking good, me excite!

dweinstein commented 10 years ago

Eagerly awaiting :+1:

spheromak commented 10 years ago

I think this is just waiting on a boot2docker from mitchellh to be made. I put up my version on vagrant cloud here: https://vagrantcloud.com/spheromak/boot2docker-0.9.0/version/1 and updated my local Vagrantfile to use them in the interim. @fnichol might make sense for you to manage that for dvm instead of relying on someone elses build ?

zaps commented 10 years ago

@spheromak whats the best way to integrate your version into dvm? Replace the override.vm.box_url line in ~/.dvm/Vagrantfile? Will that conflict with other configuration stuff that's already in the file?

Thanks

spheromak commented 10 years ago

@zaps I just built my own box and set that as the box to use in ~/.dvm/Vagrantfile

On Thu, Jun 5, 2014 at 6:58 PM, zaps notifications@github.com wrote:

@spheromak https://github.com/spheromak whats the best way to integrate your version into dvm? Replace the override.vm.box_url line in ~/.dvm/Vagrantfile? Will that conflict with other configuration stuff that's already in the file?

Thanks

— Reply to this email directly or view it on GitHub https://github.com/fnichol/dvm/pull/38#issuecomment-45295839.

zaps commented 10 years ago

@spheromak I tried doing that but dvm up seems to hang:

==> dvm: Cloning VMware VM: 'boot2docker-0.9.0'. This can take some time...
==> dvm: Verifying vmnet devices are healthy...
==> dvm: Preparing network adapters...
==> dvm: Starting the VMware VM...
==> dvm: Waiting for the VM to finish booting...

If I do a vagrant init boot2docker-0.9.0 and then vagrant up the VM boots without hanging, but of course the IP address is not configured to the 192.168.42.43. I have to vagrant ssh into the VM, check the IP address, exit the session, then update the DOCKER_HOST. It works, but kind of annoying.

So I think the dvm-provided Vagrantfile configuration is somehow causing a conflict that is preventing the VM from booting.

I don't know if it makes a difference but I'm running the latest version of Vagrant, 1.6.3.

fnichol commented 10 years ago

@zaps I was seeing the same last night after upgrading from Vagrant 1.5.4 to 1.6.3. Are you using the vmware_fusion or vmware_workstation provider by chance?

I'm tracking issues upstream in mitchellh/boot2docker-vagrant-box#48 & mitchellh/vagrant#3996

For me, downgrading to Vagrant 1.5.4 resolves this issue.

fnichol commented 10 years ago

@spheromak Also thought I'd mention that I'm testing 0.9.1 builds of boot2docker in preparation for an 0.12.0 integration as well. Currently the Mac build of Docker 0.12.0 is having a build issue (tracking dotcloud/docker#6256). Getting there, lots of rough spots at the moment :smile:

zaps commented 10 years ago

@fnichol thanks for the pointers to the upstream issues, I'm using the vmware_fusion provider.

For now the workaround I described in my earlier comment is good enough for me, as I need Vagrant 1.6 for it's Windows guest support.

fnichol commented 10 years ago

Going to pull this in…and blast on up to 1.0.0, wee!