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


Chronological Thread 
  • From: Graham Christensen < >
  • To:
  • Subject: [chef] Re: Re: Running a chef-handler via RVM-managed Ruby
  • Date: Tue, 5 Mar 2013 10:17:14 -0500

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: https://s3.amazonaws.com/gsc-vagrant-boxes/ubuntu-12.04-omnibus-chef.box

You can make this box yourself: https://github.com/grahamc/vagrant-boxes-veewee

-- 
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.

§