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

Vagrant Destroy Fails #4519

Closed
matthew-a-dunlap opened this issue Mar 16, 2018 · 3 comments
Closed

Vagrant Destroy Fails #4519

matthew-a-dunlap opened this issue Mar 16, 2018 · 3 comments

Comments

@matthew-a-dunlap
Copy link
Contributor

matthew-a-dunlap commented Mar 16, 2018

When using vagrant, if you attempt to destroy a created box it throws this error:

There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A box must be specified.

There is a workaround in our Vagrantfile (look for this line: # Uncomment this temporarily to get `vagrant destroy` to work). But using this workaround causes other issues with vagrant.

This was not a problem previously and we should find a fix to allow vagrant use to be smooth.

@pdurbin
Copy link
Member

pdurbin commented Mar 16, 2018

@matthew-a-dunlap thanks for reporting this. It's something @donsizemore and I talked about in #4384 but never resolved.

The fix might be to switch to a different base box. I'm not sure.

@matthew-a-dunlap
Copy link
Contributor Author

@pdurbin No problem. For what its worth, I uncommented the "fix" line and saw no issues in getting a vagrant box up.

pdurbin added a commit that referenced this issue Apr 22, 2020
We are deferring the rest of this work until #6849

Fixes #4519 (switched to dataverse-ansible Vagrantfile).

The guides have been updated to de-emphasize Vagrant.
@pdurbin
Copy link
Member

pdurbin commented Apr 22, 2020

I fixed this in a7c986d. Closing.

@pdurbin pdurbin closed this as completed Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants