Build the box using docker-machine instead of packer
lmakarov opened this issue · comments
I decided to try building the boot2docker-vagrant base box with docker-machine instead of packer.
I'm basically creating a copy of a docker-machine provisioned VirtualBox VM.
This approach shortens the gap between boot2docker-vagrant and docker-machine:
- no need a customized boot2docker.iso
- the base box is an exact copy of the docker-machine VM
- non-destructive updates become possible by just swapping the boot2docker.iso (though I'm not actively pursuing that idea any more)
Take a look - https://github.com/lmakarov/boot2docker-vagrant-box/tree/docker-machine
Passes all your tests ;)
Let me know what you think.
Hello @lmakarov !
It seems a great idea, since it will make more accessible the box process (packer need some learnings, and maybe it's "too much" for this box).
Could you try to open a Pull Request, and let's study code together ?
(PS : It seems you can also add a MAINTAINER file à the root of the repo, and write down your name inside with mine :) )
You guys are geniuses. 👍
Hi all, Do you know what is the status of this feature?
I'm using this Vagrant Box (Thank you for that) and maybe you can recommend me the best way to do the following:
I want to create a custom Vagrant Box that will contain some Docker Images inside. I already tested using vagrant package command after provisioning, but I think this is not the best way.
I saw that you use Packer, it is possible to do this using Packer?
@ehernandez-xk we eventually switched to docker-machine and maintain our own version of the box
https://github.com/blinkreaction/boot2docker-vagrant-box (in case you are interested).
@dduportal will know more about doing things with Packer.