Sorry, but your requested enhancements seem a bit incoherent to me. What is 
the overall goal you are trying to achieve and what properties of vagrant 
were causing you to be interested in applying it to that goal?

The "default" is a machine name; One vagrantfile can specify a number of 
machines, each with their own name, built from different prepared boxes. 
When no names are specified, you get "default".

As it is currently implemented, vagrant creates a .vagrant folder 
containing files related to the machine associated with the corresponding 
Vagrantfile. While "vagrant init" can produce a minimal Vagrantfile, most 
of the time users need to add more configuration details to the Vagrantfile 
to get what they want rather than a generic box. There's a trade-off 
between the generic-ness of the base boxes and the added complexity of the 
Vagrantfile specifications vs using a more specialized box as the base 
where the customization has been already carried out. This all means that 
the location of the Vagrantfile (you could specify VAGRANT_HOME as an 
environment variable to have it be a different location than the current 
directory) is a locus for per-machine information about the vagrant guest 
machine, a locus that can be independent of the many different providers.

While there may be some similarities between docker and vagrant, there are 
also a lot of differences, especially in the suitability for use in various 
environments.

I suspect that with Slackware on qemu you could still do an NFS-based 
shared folder. It's not as slick as a provider-supported shared folder, but 
could support your use case. Of course, that's one of the configuration 
statements that you'd need to put in a Vagrantfile.

As for your build commands, it sounds like you might want to try using the 
"shell" provisioner.


-- 
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/f949dd76-339f-405e-ba89-2c7e8edab0c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to