Create a gist now

Instantly share code, notes, and snippets.

Embed
What would you like to do?
bash -c '
<%= "export http_proxy=\"#{knife_config[:bootstrap_proxy]}\"" if knife_config[:bootstrap_proxy] -%>
yum install -y wget
wget <%= "--proxy=on " if knife_config[:bootstrap_proxy] %>http://rbel.co/rbel5
rpm -Uvh rbel5
yum install -y rubygem-chef
'
@srininara

This comment has been minimized.

Show comment
Hide comment
@srininara

srininara Apr 30, 2013

I am trying to use this for the prepare step. Only catch is that yum installs an older version of chef (0.10.6). I am not able to find a way yet to overcome this. Any suggestions would be of great help.

I am trying to use this for the prepare step. Only catch is that yum installs an older version of chef (0.10.6). I am not able to find a way yet to overcome this. Any suggestions would be of great help.

@ikiselev

This comment has been minimized.

Show comment
Hide comment
@ikiselev

ikiselev Jan 20, 2016

Trying to prepare debian jessie. Got error (with -VV option): "E: Package 'libopenssl-ruby' has no installation candidate".
So, "apt-get install" exited (with error code, i suggest, that was not checked by "prepare" command). Hope this gist helps me to write own prepare command.

Trying to prepare debian jessie. Got error (with -VV option): "E: Package 'libopenssl-ruby' has no installation candidate".
So, "apt-get install" exited (with error code, i suggest, that was not checked by "prepare" command). Hope this gist helps me to write own prepare command.

@bby-bishopclark

This comment has been minimized.

Show comment
Hide comment
@bby-bishopclark

bby-bishopclark May 15, 2018

@srininara - are you still seeing an old chef version? Specifying the right repo URL could help it choose something newer: http://packages.chef.io/repos/yum/stable/el/7/x86_64/ .

@srininara - are you still seeing an old chef version? Specifying the right repo URL could help it choose something newer: http://packages.chef.io/repos/yum/stable/el/7/x86_64/ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment