Peter, were you literally trying --no-provisioning or just --no-provision as it is printed in their documentation? --no-provision is equivalent to the command for vagrant up and other machine control commands.
On Sunday, April 3, 2016 at 2:01:52 PM UTC-5, Peter Fokkinga wrote: > > Hi all, > > When I execute "vagrant snapshot restore base" in the directory that has > the Vagrantfile vagrant is always running the defined provisioners. > > How can I prevent this? > > I tried "--no-provisioning" as described in > https://www.vagrantup.com/docs/cli/snapshot.html but > vagrant snapshot restore --no-provisioning base > gives "An invalid option was specified. " whereas > vagrant --no-provisioning snapshot restore base > simply goes on with provisioning. > > Even run: "once" provisioners are executed at every restore. > > This is with Vagrant 1.8.1 with VirtualBox 5.0.16 on OSX > > Regards, Peter > -- 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/175ac855-1a09-4485-8e50-b58dfdce0935%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
