Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Docker packaging for Vagrant #1660

Closed
wants to merge 3 commits into from
Closed

Conversation

zimbatm
Copy link
Contributor

@zimbatm zimbatm commented Aug 24, 2013

This is a first run to package docker in a nice pre-built vagrant box. It's not finished yet but I thought it might be better to avoid duplicating the effort. Feel free to take over as I'm going to be quite busy for a while.

The current build uses packer, the build tool developed by the same guy that's behind vagrant. It supports only 3 vagrant targets (VirtualBox, VMWare Fusion, AWS) for the moment but more are surely to come. For now only VirtualBox is tested and VMWare is supposed to work but I didn't have it available on my computer.

The build installs Ubuntu 12.04.3 with the raring (3.8) kernel, a minimal set of dependencies and the new docker 0.6.
Install packer and run packer --only=virtualbox template.json to get the output (~280MB)

There's still a couple of things I wanted to check out:

  • the .sock file is not accessible from the vagrant user
  • play more with the install to make sure docker is working properly
  • see if it's an issue that the manpages are missing (this keeps the box lighter)

That's it for now. Feel free to close if you feel this is not needed I won't get offended :)

@crosbymichael
Copy link
Contributor

ping @mzdaniel

@zimbatm
Copy link
Contributor Author

zimbatm commented Sep 4, 2013

I don't know. I guess the "vmware" target works for both Fusion and
Workstation but I don't have a license handy.

On 3 September 2013 07:44, demon012 notifications@github.com wrote:

Does packer not also support VMWare Workstation as Vagrant does?


Reply to this email directly or view it on GitHubhttps://github.com//pull/1660#issuecomment-23717785
.

@mzdaniel
Copy link
Contributor

mzdaniel commented Sep 6, 2013

Thank you @zimbatm. I think is useful and others can benefit. If you are willing to maintain it and improve it, I would suggest to move the PR coherently into /contrib.

@zimbatm
Copy link
Contributor Author

zimbatm commented Sep 16, 2013

Actually I was thinking that it would be beneficial to have it built
automatically on each release and then you could use it in the main
Vagrantfile instead of maintaining that hacky kernel-swapping hack.

Otherwise it might be simpler to move it to a separate repo and call it a
day.

On 6 September 2013 15:53, Daniel Mizyrycki notifications@github.comwrote:

Thank you @zimbatm https://github.com/zimbatm. I think is useful and
others can benefit. If you are willing to maintain it and improve it, I
would suggest to move the PR coherently into /contrib.


Reply to this email directly or view it on GitHubhttps://github.com//pull/1660#issuecomment-23974476
.

@crosbymichael
Copy link
Contributor

I think right now contrib or a separate repo would be best. Things are still moving quickly with our build and processes.

What do you think @zimbatm ? I'm going to close this for now, feel free to reopen when it has been moved to contrib or let us know the url if you decide to move this to your own repo. Thanks.

@zimbatm
Copy link
Contributor Author

zimbatm commented Oct 5, 2013

Agreed. Just wanted to add that I found an existing separate project that does exactly the same (but better) as this branch: https://github.com/mitchellh/packer-ubuntu-12.04-docker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants