This content has moved to http://www.opscode.com/chef/install/, but is being retained for legacy purposes.
The Chef Full Installer has been tested with Debian, Ubuntu, CentOS, RHEL, Fedora, Oracle Linux, Scientific Linux, and OS X.
You can install it by entering this command:
Once it is installed there will be no icon for it. If needed, you can confirm it was installed correctly with these commands in a new command prompt window:
You should see "10.18.0" returned as the version number.
Upon installation, this script will:
After installation, you should move your validation client's private key onto the node and copy it to
The initial configuration of a chef-client requires a
Chef client has a number of configuration settings that do not appear above. See Chef Configuration Settings for further details.
It is often easiest to install Chef on a node using knife-bootstrap. Bootstrapping runs a script on the target system which install Ruby, install chef-client, configure chef-client, and start a chef-client run. This method requires the node to be accessible over SSH. In most cases, bootstrapping a new node will be as simple as running a single command. For instance, to bootstrap a Linux workstation using the Omnibus installation method you might run the following command:
See Knife Bootstrap and Launch Cloud Instances with Knife for complete documentation. The bootstrap scripts distributed with knife for Ubuntu use an install method similar to the installation methods above.
There are a few ways that the Omnibus install is different from installing through rubygems or your OS's packaging system such as 'yum' or 'apt'.
Tested Operating Systems
Omnibus will work to install Chef on many Linux operating systems and OS X. It has been tested with Debian, Ubuntu, CentOS, RHEL, Fedora, Oracle Linux, Scientific Linux, and OS X. You can find information on installing the Windows version of Omnibus on the Installing Chef Client on Windows page.
The Omnibus installers are built using the same Ruby based Open Source project we use for packaging Private Chef. A couple of the installers are built with older build systems, and we plan to migrate them in the coming months. We also expect to add more platforms in the future.
Omnibus wraps itself in a package specific to your distribution where possible, such as a deb or rpm, so you can easily manage it using the tools you’re familiar with. If you prefer regular packages or installing from Rubygems for policy or personal reasons, you can find links to those directions on the Installing Chef Client and Chef Solo page.
Embedded Ruby and Other Dependencies
The Omnibus installer includes the Chef client, a stable version of Ruby, and everything else needed for Chef to run, in a single package. The dependencies are all carefully embedded so they won’t conflict with other versions of the same software on your system. Because you are also using an embedded version of rubygems you'll want to use a command like "sudo /opt/chef/embedded/bin/gem install knife-PLUGIN" to install any knife plugins on an Omnibus workstation.
Chef_gem and Gem_package resources
Because Omnibus includes its own version of Rubygems, it is important that you correctly use the gem_package and chef_gem resources. The gem_package resource is for installing a gem package to your system, whereas the chef_gem resource is for install a gem for use inside a chef recipe. Additional information is available on the Resources wiki page.