Closed Falkor closed 6 years ago
@Falkor I'm sorry to have to say this, but I have no idea :(
I haven't used this project myself in over 3 years. At a minimum, I can say that the newest versions the automated tests run against are ruby 2.0.0 and Vagrant 1.7.0.
My guess would be that either Vagrant 2, or the Ruby 2.3.4 or 2.4.0 that it now uses broke compatibility with this project.
I feel bad having to say this, but I no longer have the ability or desire to maintain this project. If you happen to know someone who would like to take it over, I'd be more than happy to set that up.
Closing as stale.
I managed to get it working with Vagrant 2.1.2 running the following command:
gem install puppet -v 4.10.12 --install-dir ~/.gem/ruby/2.4.0
(I'm still using Puppet 4.10.12, your version of Puppet might be different.) I hope this helps somebody.
Also if all else fails, the very dirty workaround I came up with is
# vagrant up 2>&1 | grep 'Command: ' | sed 's/^Command: //' | while read -r line; do sh -c /usr/local/bin/${line}; done
It's very dirty, but when in a bind it's better than copy pasting the command lines.
I have installed the
vagrant-r10k
plugin, together with the puppet gem as suggested:The project I'm using (relying on RVM and Gemset) has the following structure:
The
puppet/Puppetfile
has the following content:Finally, the configuration for vagrant-r10k in the root
Vagrantfile
is as follows:Now if I invoke
vagrant {up,provision}
, I get the following error:of course repeated for each module in the
Puppetfile
. It looks like the gem path to the vagrant plugin is ignored... Any hint?