Question

bundle exec fails when called from an init.d script

I am trying to set up my server to use chruby to manage rubies and have unicorn started from a rails app bundle.

service unicorn start works fine from a shell. /etc/init.d/unicorn is calling a chruby wrapper for unicorn that calls bundle exec unicorn.

During the init process, bundle exec fails unable to “re-resolve” dependencies before running unicorn. It appears that it can’t contact the gem sources to resolve things.

Can this be disabled or worked around somehow?

The message is:

Found changes from the lockfile, re-resolving dependencies because bundler is unlocking Could not find gem ‘blah’ in any of the gem sources listed in your Gemfile.

Any pointers would be greatly appreciated. Thanks.

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Adding BUNDLE_PATH directly to the app’s .bundle/config and re bundling, appears to have fixed the issue.

This comment has been deleted