Starting a VM without re-running provisioning
600 views
Skip to first unread message
Chris Beauchamp
Jan 27, 2011, 4:02:41 AM1/27/11
to Vagrant
Just starting using vagrant for development and testing (it is *very*
good), but is there a way to start a vagrant VM *without* re-running
the provisioning. I know you can suspend and resume but sometimes you
need to halt the VM and restart it, but there may be changes to it
which you don't want to be deployed.
I can't find anything that will do this, I guess, apart from just
starting it in VirtualBox, but that seems a bit wrong headed.
Any thoughts?
Chris
good), but is there a way to start a vagrant VM *without* re-running
the provisioning. I know you can suspend and resume but sometimes you
need to halt the VM and restart it, but there may be changes to it
which you don't want to be deployed.
I can't find anything that will do this, I guess, apart from just
starting it in VirtualBox, but that seems a bit wrong headed.
Any thoughts?
Chris
Mitchell Hashimoto
Jan 27, 2011, 4:12:46 AM1/27/11
to vagra...@googlegroups.com
Chris,
There is `vagrant up --no-provision` available. This is only available
with `up`, but I'd like to make this work with `reload` too
eventually.
Best,
Mitchell
Chris Beauchamp
Jan 27, 2011, 4:35:28 AM1/27/11
to Vagrant
Hi Mitchell,
Brilliant! Hadn't spotted that.
Thanks
Chris
On Jan 27, 9:12 am, Mitchell Hashimoto <mitchell.hashim...@gmail.com>
wrote:
Brilliant! Hadn't spotted that.
Thanks
Chris
On Jan 27, 9:12 am, Mitchell Hashimoto <mitchell.hashim...@gmail.com>
wrote:
Thibaut Barrère
Jan 29, 2011, 5:52:18 AM1/29/11
to Vagrant
> Brilliant! Hadn't spotted that.
Me neither, will be useful, thanks!
@Chris: if you're like me, you'll quickly find it addictive to be able
to keep one vagrant per project and be able to "vagrant up" and find
all your dbs with correct version and data up and running, with
exactly the configuration used in production.
I'm on Mac OS X but I never run redis/mongodb or other outside
vagrant, actually!
-- Thibaut
Chris Beauchamp
Jan 31, 2011, 4:34:10 AM1/31/11
to Vagrant
On Jan 29, 10:52 am, Thibaut Barrère <thibaut.barr...@gmail.com>
wrote:
> > Brilliant! Hadn't spotted that.
>
> Me neither, will be useful, thanks!
>
> @Chris: if you're like me, you'll quickly find it addictive to be able
> to keep one vagrant per project and be able to "vagrant up" and find
> all your dbs with correct version and data up and running, with
> exactly the configuration used in production.
Yup, I'm generally Sysadmin type, but looking forward to knowing our
>
> Me neither, will be useful, thanks!
>
> @Chris: if you're like me, you'll quickly find it addictive to be able
> to keep one vagrant per project and be able to "vagrant up" and find
> all your dbs with correct version and data up and running, with
> exactly the configuration used in production.
developers will actually be testing/developing on something that's
identical to production.
Thanks to all the vagrant developers!
Chris
Patrick Connolly
Oct 29, 2011, 2:20:10 PM10/29/11
to vagra...@googlegroups.com
Seems --no-provision flag is broken in 0.8.7 -- still runs provisioner for me. Can anyone else confirm?
Adam Jenkins
Oct 29, 2011, 4:50:49 PM10/29/11
to vagra...@googlegroups.com
I noticed this yesterday.
Patrick Connolly
Jan 9, 2012, 6:33:26 PM1/9/12
to vagra...@googlegroups.com
bump? can anyone else confirm that --no-provision is broken?
Mitchell Hashimoto
Jan 9, 2012, 6:36:43 PM1/9/12
to vagra...@googlegroups.com
It is broken in currently released Vagrant.
It is fixed in git.
Mitchell Hashimoto
Jan 11, 2012, 12:30:53 AM1/11/12
to vagra...@googlegroups.com
Note that there is now an acceptance test to verify this flag works now and forever onward.
:)
Patrick Connolly
Jan 11, 2012, 2:42:15 PM1/11/12
to vagra...@googlegroups.com
Whoop whoop!
< / valuable-contribution>
Reply all
Reply to author
Forward
0 new messages