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 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 vagrant" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1708125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs