Thanks for your reply. Nothing automated in the bash profile/rc for sure.
And I know I can manually force the box to get a new IP address. I thought
all this will be managed by vagrant. That's what I want to use it for
anyways. I haven't checked the host file yet. That could be a probable
reason.
Hi,
A more lightweight approach would be to distribute a default Vagrantfile
and ask users to put it in their ~/.vagrant.d/ directory
You could enable / disable your company specific defaults with an env var
for example
Cheers,
Torben
Am 10.10.2014 01:57 schrieb Chris Chalstrom
Hi Jamie,
Am 09.10.2014 17:25 schrieb Jamie Jackson jamieja...@gmail.com:
Thanks, Torben,
First impressions, below...
Thanks for the links,
Jamie
On Thu, Oct 9, 2014 at 1:14 AM, Torben Knerr torben.kn...@gmail.com
wrote:
Hi Jamie,
sounds familiar.
You might also be interested in:
Hi,
I'm getting an error from certain Vagrantfiles; I spent a long time with
someone on the #vagrant irc channel trying to fix this and s/he suggested
that there was likely a problem with VagrantCloud. Can I check that this is
so, and whether there's a way to alert them, and whether there's
Hi Tom,
Looks like you're using Vagrant version 1.3.5. You need 1.5 to use
Vagrant Cloud and related features. See
here: https://vagrantcloud.com/help/vagrant/cloud/vagrant-1-5
Best,
Jack
On Friday, October 10, 2014 12:34:45 PM UTC-4, Tom Ash wrote:
Hi,
I'm getting an error from certain
Hi,
Yes, I have now tried it with centos:centos6. Documentation incorrectly
mentions centos:6. That still yields that error response. So how would I
add a command and what command? The vagrant docs don't mention this. I was
planning to provision the box with ansible. Does anyone know of an
Hello
I will insist on you should do some docker test outside vagrant to see what
docker does,
https://www.docker.com/tryit/
you back? cool, welcome back.
imagine docker create a vm that does nothing, since that is what docker is,
a 100% isolated enviroment.
Is more similar to what chroot is,
