Skip to content
This repository has been archived by the owner on Apr 2, 2020. It is now read-only.

Allow using alternative Vagrant providers such as Vmware #11

Open
jezdez opened this issue Dec 29, 2013 · 9 comments
Open

Allow using alternative Vagrant providers such as Vmware #11

jezdez opened this issue Dec 29, 2013 · 9 comments

Comments

@jezdez
Copy link

jezdez commented Dec 29, 2013

No description provided.

@bfirsh
Copy link
Collaborator

bfirsh commented Dec 30, 2013

In theory this should just be a matter of building a VMware Vagrant box with Packer and setting the VAGRANT_DEFAULT_PROVIDER environment variable on first run.

@julien-duponchelle
Copy link
Owner

The image is built from this packer file:
https://github.com/mitchellh/packer-ubuntu-12.04-docker

@bfirsh
Copy link
Collaborator

bfirsh commented Dec 30, 2013

I'll build a VMware image. I want to move the VirtualBox image to a new S3 bucket anyway.

@julien-duponchelle
Copy link
Owner

Perhaps we can use the release system of Github in order to store the image

@bfirsh
Copy link
Collaborator

bfirsh commented Dec 30, 2013

There's a fairly small file size limit IIRC. Can't find out exactly what it is though.

@bfirsh
Copy link
Collaborator

bfirsh commented Dec 30, 2013

And there's a chicken/egg problem there too – we need to put the release URL in the docker script, but we need tag the docker script before we can get a release. Argh.

@julien-duponchelle
Copy link
Owner

You are right 1GB by repository . S3 is a better way to distribute expect it cost money.

@bfirsh
Copy link
Collaborator

bfirsh commented Dec 30, 2013

I'll put it on the @orchardup S3 account and we can cover the cost. Shouldn't be much. :)

@jezdez
Copy link
Author

jezdez commented Dec 30, 2013

Yays \o/

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

No branches or pull requests

3 participants