-
http://www.manning-sandbox.com/thread.jspa?messageID=168076#168076
-
running `vagrant up` from inside your repo was complaining about "path', this fixed it:
> * `path` for shell provisioner does not exist on the host system: /root/vagrant/lab/ConfigureRemotingForAns…
avuko updated
4 years ago
-
Creates a base Vagrantfile with custom settings to allow running boxes on HyperV.
Example:
```
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure('2') do |config|
config.vm.box =…
-
I think it would be good to have a vagrant file for testing, aslo a part of this role seems a bit untidy. I will fork and make a pull request.
-
All plugins should be installable in a sandbox in order to allow to run different Vagrant files with different versions of the same plugin.
-
Right now, Vagrantfiles are a mix of configuration of the guest machine being built + personal local configuration.
As in this commit setting up a synced folder - https://github.com/shedd/duckpan-vag…
shedd updated
10 years ago
-
I have often come across interesting Vagrant setups for testing components. The original source repo for this project - https://github.com/L2G/duckpan-vagrant - was one such example. (Another exampl…
shedd updated
10 years ago
-
When I run `vagrant up` I get the following errors and the provisioning doesn't complete.
```
==> bundlegen: Running provisioner: shell...
bundlegen: Running: inline script
bundlegen: GOO…
-
Create an option to output Vagrantfile
-
Magma VMs use bare Ubuntu boxes from the Vagrant Cloud as basis for some VMs. However, two different bare boxes are used, `generic/ubuntu2004` and `ubuntu/focal64`. This introduces complexity in maint…