A better way to do this is to run vagrant like
env -u GEM_HOME -u GEM_PATH vagrant
because one might want to actually have those variables set in their
shell configuration. I have aliased that command to "vagrant" in my
shell initialisation file.
--
You received this bug notification
Simple make sure you don't have any old GEM_HOME or GEM_PATH variables hanging
around, for example, run
env|grep GEM_
and see if anything is returned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have this same issue, can you please explain how you managed to fix it
in more detail?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708125
Title:
vagrant fails with error "can't find gem
This bug report is being closed due to your last comment. For future
reference you can manage the status of your own bugs by clicking on the
current status in the yellow line and then choosing a new status in the
revealed drop down box. You can learn more about bug statuses at
It turned out that I had GEM_HOME and GEM_PATH still set from a setup on
another machine, which caused ruby the search the wrong path. After
getting rid of those, everything works as expected.
This bug report can be closed, afaic.
--
You received this bug notification because you are a member
