[chef] Re: Re: Re: Re: Running a chef-handler via RVM-managed Ruby


Chronological Thread 
  • From: Cassiano Leal < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Running a chef-handler via RVM-managed Ruby
  • Date: Tue, 5 Mar 2013 14:21:07 -0300

Thanks for the inputs. I have downloaded the bento prebuilt ubuntu-12.04 basebox.

Now what's happening is that the handler can't find the gem at all. My guess is that it's running using Chef's omnibus Ruby, while the gem was installed in the RVM-managed Ruby.

That just came full circle, and I'm once again trying to understand if there's a way to run the handler using RVM.

Either that, or installing the gem onto Chef's Ruby.

Thanks!
- cassiano

On Tuesday, March 5, 2013 at 13:25, Sean OMeara wrote:

Bento is the recommended way to roll Vagrant boxes for Chef.


-s

On Tue, Mar 5, 2013 at 10:17 AM, Graham Christensen < "> > wrote:
Hi Cassiano,

Most of the boxes available for Vagrant aren't using omnibus installations.
You can make your own, Veewee makes this process very simple.

I have done this myself:

You can make this box yourself:

--
Graham Christensen

On Tuesday, March 5, 2013 at 10:06 AM, Mike wrote:

It looks like your vagrant box is executing Chef under the
Vagrant-execution ruby 1.8.

Have you tried running this with an Omnibus-built Chef-Client on Vagrant?

-M

On Tue, Mar 5, 2013 at 9:56 AM, Cassiano Leal < "> >
wrote:

Is it possible? :)

My problem is that I have a report handler that posts stats to stathat.com,
and the gem is incompatible with ruby 1.8 (or so I figured).

All my systems have 1.9.3 installed via RVM, and I want to use that for the
handler. The gem installs ok using fnichol's rvm cookbook's gem_package
recipe, but the handler still tries to run on the system Ruby (or the
omnibus Ruby, maybe?) [0].

Any clues?

Thanks!

- cassiano





Archive powered by MHonArc 2.6.16.

§