I'm currently running vagrant version 1.7.2, I don't believe I've ever
updated. I'm going to try now.
I've recently installed vagrant-hostsupdater and vagrant-triggers.
Rebooting my machine didn't improve things.
Don't think I've got any nested vms going.
On Thursday, January 28, 2016 at
>
> This is outrageous, the official tutorial leads directly into this trap!
> How can that possibly be? Just did
> https://www.vagrantup.com/docs/getting-started/synced_folders.html and
> run into same issue, was not able to solve until found this post.
> >after "vagrant up", I hit "pwd" and
This is outrageous, the official tutorial leads directly into this trap!
How can that possibly be? Just
did https://www.vagrantup.com/docs/getting-started/synced_folders.html and
run into same issue, was not able to solve until found this post.
>after "vagrant up", I hit "pwd" and got
On Fri, Jan 29, 2016 at 12:47 AM, Tomasz Majchrowski wrote:
>
> Now we would like to use the same "customer docker host" across all
> environments (including Linux based one).
Hello,
yes is possible.
have a look at this parameter:
Hi All,
On platforms that don’t support containers (e.g. Windows) by default
Vagrant spins up a Tiny Core Linux (boot2docker) Docker host. In addition
it's provide possibilities to run Docker containers in a custom Docker host
over "vagrant_vagrantfile" configuration parameter. This works
Thanks so much for the responses, I found the plugin with desire behavior
at smdahlen / vagrant-hostmanager
On Tuesday, January 26, 2016 at 8:15:42 PM UTC-8, Stathy Touloumis wrote:
>
> Is there documentation as to how I can capture machine information that
> can be used during the provision