Sounds like you're wanting a statically built copy of ruby.The issue you're seeing is because the operating system's dynamic linker hasn't been updated to look for library objects in chef-client's lib path. Normally this would happen during package installation.
--~jHi Ranjib,By portable I meant just copying the chef folder. I want to avoid installing chef-client if possible. On Windows, I can take the chef-client install folder, copy that to other location or machine and run the chef-client. That doesn't work on linux. I see the following error:../embedded/bin/ruby: error while loading shared libraries: libruby.so.2.1: cannot open shared object file: No such file or directoryThanksOn Mon, Jun 8, 2015 at 3:05 PM, Ranjib Dey < " target="_blank"> > wrote:omnibus installers are fairly portable as long as your platforms are same. how are you generating the installers? or how are you packaging your app+ chef. I use fpm to repackage omnibus chef with additional gems (like ruby-lxc) and then use chef-client in localmode (which is pretty much same as solo).What error you are seeing?On Sun, Jun 7, 2015 at 10:38 PM, Naresh < " target="_blank"> > wrote:Hi everybody,We are trying to use chef-solo to install our application on linux. We plan to distribute chef (chef-client install folder) along with our application files and when user runs an install script, chef-solo will be invoked. End-user need not know that we are using chef-solo. I have copied chef folder on a different machine and tried to run a simple recipe with no success.Have any of you tried such thing? Is there a portable chef-client?--Regards
Naresh--Regards
Naresh
Archive powered by MHonArc 2.6.16.