Thanks, Teemu. That works perfectly.
Another solution I found was to move the vagrant user's setting of GEM_HOME
from .bashrc to .bash_profile. After that move, /home/vagrant/gems no
longer appeared as a gem path when running via sudo -E.
Alex
On Tue, May 6, 2014 at 10:10 PM, Teemu
Hi everyone,
I'm upgrading from Vagrant 1.0.7 to 1.5.4. Things are mostly working except
that this change[1], which makes sudo commands run with -E (preserve
environment), causes chef-client to load a version of the Yajl gem from the
vagrant user's gem path rather than from chef's embedded
Hi Alex,
You should be able to set GEM_HOME with `chef.binary_env` attribute, like
this: https://gist.github.com/tmatilai/9376993
--
Teemu
On Tue, May 6, 2014 at 11:44 PM, Alexander Kahn alexanderk...@gmail.comwrote:
Hi everyone,
I'm upgrading from Vagrant 1.0.7 to 1.5.4. Things are
