Hi all, This is part question and part request for comment.
I've become more familiar with Docker and I'd like Vagrant to be patterned similarly. E.g. docker images produces a list of images. vagrant box list produces a list of boxes. This is good. However, docker ps -a produces a listing of containers, whereas vagrant global-status produces a list of "machines". This is fine. My question is: Why do I need to have an environment tied to a directory/folder? What I'd like to do is: vagrant up --provision-from-box "some/box" --name "some-new-machine-name" Instead of having to rely on a Vagrantfile to define a "machine". Plus, when I do want to use a Vagrantfile, I'd like to do the following: vagrant up -f Vagrantfile.mymachine In other words, is it really necessary to have one Vagrantfile per directory? to define an environment for a machine? -- 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/fa49f073-fa4c-4aef-bad9-7544ddd23778%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
