Thank you so much for your help Alvaro.
I did actually try creating the /vagrant directory in the VM from which I
made the box and when I run it, there was a complaint when it made /vagrant.
Not sure if this is a bug because though the output lists the command, it
gives no output.
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => D:/Vagrant_examples/mint182_base
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
Stderr from the command:
PS D:\Vagrant_examples\mint182_base>
So I am guessing that when it created /vagrant, the output (either stdout
or stderr) was "already exists" but this is not displayed.
No problems though, I can remove /vagrant in the original VM and create a
new box.
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/c61e810f-def0-4639-95a5-ec3dbdd7d9ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
