Cinc Client
A free, fully compatible distribution of Chef Infra Client. Drop-in replacement for chef-client.
Install
Using the install script
The Cinc Project mirrors Chef’s omnibus installer at omnitruck.cinc.sh. To install the latest 19.x of Cinc Client:
curl -L https://omnitruck.cinc.sh/install.sh | sudo bash -s -- -v 19. { iwr -useb https://omnitruck.cinc.sh/install.ps1 } | iex; install -version 19Using bundler
Gems are published to rubygems.cinc.sh:
source "https://rubygems.cinc.sh" do
gem "chef-bin"
endOr with plain rubygems:
gem install chef-bin --clear-sources -s https://rubygems.cinc.sh -s https://rubygems.orgPlain packages
Packages for all supported platforms are at downloads.cinc.sh/files/stable/cinc/.
Container image
We publish a cincproject/cinc container image on Docker Hub, primarily for use with kitchen-dokken. See Container images for tagging scheme and usage examples.
Testing cookbooks with Cinc
Use kitchen-cinc or kitchen-dokken (2.23.0+) to point Test Kitchen at Cinc Client instead of Chef Infra Client. Both ship with Cinc Workstation.
As part of Workstation
The Cinc Client is also included in Cinc Workstation.
Configuration
Cinc Client reads its configuration from:
/etc/cinc/client.rbon UNIX/Linux/macOSC:\cinc-project\client.rbon Windows
Migrating from Chef? Configurations are compatible — symlink or copy your existing client.rb as-is.
Usage
cinc-client and the associated tools are fully compatible with chef-client. A chef-client wrapper is installed that redirects to cinc-client, so existing automation keeps working.
All upstream documentation and Chef classes apply.
knife bootstrap must be called with --msi_url <direct url to MSI> to correctly bootstrap a Windows node to Cinc Client. The MSI for your version lives at downloads.cinc.sh/files/stable/. We’re tracking a better UX in GitLab.#community-distros on the Chef Community Slack, or open an issue on GitLab.