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

mis-matched box name between packer script and VagrantFile #72

Open
tmcgee opened this issue Apr 29, 2014 · 3 comments
Open

mis-matched box name between packer script and VagrantFile #72

tmcgee opened this issue Apr 29, 2014 · 3 comments
Labels

Comments

@tmcgee
Copy link
Member

tmcgee commented Apr 29, 2014

The packer script build.sh adds the newly create Vagrant box with a name of "welldone_server".

The VagrantFile is looking for the box named "welldone/strato-base" which it does not find locally so attempts to download the 0.1 version from vagrantcloud.

This applies to virtualbox-iso. I presume it would apply to the other providers as well.

@amcgee
Copy link
Member

amcgee commented Apr 29, 2014

Does changing the name of the box prevent the download? I think it might
still check vagrant cloud...
On Apr 29, 2014 7:13 AM, "Tim McGee" [email protected] wrote:

The packer script build.sh adds the newly create Vagrant box with a name
of "welldone_server".

The VagrantFile is looking for the box named "welldone/strato-base" which
it does not find locally so attempts to download the 0.1 version from
vagrantcloud.


Reply to this email directly or view it on GitHubhttps://github.com/WellDone/Strato/issues/72
.

@tmcgee
Copy link
Member Author

tmcgee commented Apr 29, 2014

I tested this. It does not prevent the download. I believe that is because of mismatch on the vagrant version number. That issue is being added now.

@tmcgee
Copy link
Member Author

tmcgee commented Apr 29, 2014

Commenting out the build number requirement in VagrantFile allows the local box to be used and no download occurs.

The VirtualBox VM boots but fails to mount guest folders. Will check my configuration and potentially add that as a new issue

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

No branches or pull requests

2 participants