-
Notifications
You must be signed in to change notification settings - Fork 70
Use boot2docker instead of Ubuntu #17
Comments
PS: I have worked with steeve the author of boot2docker in a previous company, it's a small world :) |
Small world indeed. @josephschorr is interested in working on this too. |
At the moment getting docker-osx to build on Vagrant is not straight forward: It would be brilliant to do this without Vagrant, but I haven't investigated the complexity of that. |
+1 on using boot2docker :) |
https://github.com/mitchellh/boot2docker-vagrant-box now it IS more than straightforward! |
My 2cents on this whole thing is that the docker-osx api is basically perfect for most usages. The only things it could change underneath are dropping vagrant and using |
Agree - I liked docker-osx and boot2docker image seems perfect. The localdocker convention for the guest VM I think is a great one to encourage - over port forwarding (keep port forwading for only docker and ssh ports). I have seen people tripped up, many times, when trying to run an image (often based on the Vagrantfile in the docker repo) as one of the 40K port ranges it wants to forward is in use by Skype or other desktop tools. This is good stuff! |
As long as we keep synced folders. The https://github.com/mitchellh/boot2docker-vagrant-box project seemed to lose synced folders support when using boot2docker ISO due to lack of guest additions. I think the request in this ticket is equivalent to https://github.com/fnichol/dvm project? |
yes likely so. Running ubuntu isn't too bad for when you do want to ssh in and run thing in linux (when debugging interaction with the the docker client - you really want to do that). I wonder if the memory footprint is that different - I didn't notice boot2docker was really much better for me in either disk/download or memory (but I didn't look close). |
Boot2docker is lighter than ubuntu:
https://github.com/steeve/boot2docker
The text was updated successfully, but these errors were encountered: