-
Notifications
You must be signed in to change notification settings - Fork 32
Cannot execute bundle
#100
Comments
I have the same problem 👍 |
If you do |
Yes, I can |
In our case this issue turned out to be sudo complaining about not being able to resolve hostname. Ours was a system begins auto scale so we didn't really care about hostname. Maybe the task that checks return code should only look at last line? |
Ran into this problem as well. For me this problem occurred due to a stray "export" in .bashrc, causing the environment variables to be printed at each login. I think this error can pop up if locales are misconfigured as well. Even if the code is ok, at the very least the error message is misleading. It is in some cases possible to execute bundler even if exit_code_as_app of 'bundler --version' != 0. |
Actually, this code fails with -su: bundle: command not found:
Clarification, I use rbenv to manage this appuser |
@pkordel have you managed to get recap to work with rbenv? |
I've just started new server to test recap. Ran into this issue:
If i ssh to server using my account I am able to execute failing command successfully:
If i login to
backoffice
acccount (application user). I am able to do:Which seems to be fine. I've tried to install ruby to the system, rvm and rbenv. All ending with the same error. Obviously I am missing something.
Thx for any hint.
The text was updated successfully, but these errors were encountered: