Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms


anaconda (12) Versions 0.7.2

Installs/Configures anaconda

cookbook 'anaconda', '~> 0.7.2'
cookbook 'anaconda', '~> 0.7.2', :supermarket
knife supermarket install anaconda
knife supermarket download anaconda
Quality 75%

anaconda cookbook

This cookbook is now up for adoption! See for details.

Chef cookbook for installing Continuum Analytic's Anaconda: "completely free Python distribution for large-scale data processing, predictive analytics, and scientific computing". Specifically:

  • Anaconda 2.2, 2.3, 4.4.0, 5.0.1 (the default)
    • python2 or python3
    • x86 or x86_64
  • Miniconda
    • python2 or python3
    • x86 or x86_64
  • Usage tested on Ubuntu, unittested on Debian, CentOS, and RedHat. See [rspec tests](spec/default_spec.rb#L101) and [kitchen tests](.kitchen.yml#L18) for the full list.

This also serves as an example for developing and testing Chef cookbooks. It uses:

  • ~ChefDK~ Given up on this for now; uses standard RVM and Gemfile to manage installation
  • RSpec (3.7)/Chefspec (7.1) for unit testing

In addition:

  • Vagrant to provide an out-of-the-box working example; only tested with 2.0.


If you want to just have a working Anaconda VM, install:

For the full experience (e.g. running the test suite), also install:


The sample [Vagrantfile](Vagrantfile) will build you an Anaconda VM with no changes necessary; note it might take a few minutes to download the Anaconda installer itself.

  $> vagrant up --provision

  # the sample image includes `recipe[anaconda::shell_conveniences]`, which
  # means conda is already in PATH via /etc/profile.d
  $> vagrant ssh
  $vagrant> conda --version
  conda 4.3.30

  # or you add it to PATH manually
  $> vagrant ssh
  $vagrant> export PATH=/opt/anaconda/5.0.1/bin:${PATH}
  $vagrant> conda --version
  conda 4.3.30

It includes a Jupyter notebook server accessible at Token authentication is disabled in the quickstart Vagrant setup.

Lastly, to use it in a cookbook:

  include_recipe 'anaconda::default'

Warning! If you're also using the python cookbook...

You MUST include recipe[anaconda::python_workaround], otherwise subsequent chef runs will fail. See the issue for details.

Usage, recipes, attributes, and resources

The main recipe is anaconda::default. Include it in your runlist, and it will install the package as well as any necessary dependencies.

The following are user-configurable attributes. Check [attributes/default.rb](attributes/default.rb) for more details.

  • anaconda
    • version: the Anaconda version to install. Valid values are:
    • 2.2.0
    • 2.3.0
    • 4.4.0
    • 5.0.1
    • latest (for miniconda only)
    • python: which version of Python to install for. Valid values are:
    • python2
    • python3
    • flavor: what architecture the instance is. Valid values are:
    • nil (will autodetect)
    • x86 (32-bit)
    • x86_64 (64-bit)
    • install_type: which Anaconda distribution to install. Valid values are:
    • anaconda
    • miniconda
    • install_root: the parent directory of all anaconda installs. note that individual installs go into #{install_root}/#{version}
    • accept_license: must be explicitly set to the string yes (there are no defaults); any other value will reject the license.
    • owner: the user who owns the install
    • group: the group who owns the install
    • system_path: adds the bin path to the system's profile.d directory


Include this to have the environment set for all users (login shells) via /etc/profile.d. Useful for development.

resource anaconda_package

You can use the anaconda_package resource to install new packages into the Anaconda environment:

  # I don't know what 'astroid' is, just using it as a sample package
  anaconda_package 'astroid' do
    # the other supported action is `:remove`
    action :install

See the [resource definition](resources/package.rb) for additional options; in general, all it does is present the same options as conda install/conda remove.

resource anaconda_nbservice

This only works with a full Anaconda installation! I.e. the notebook service will not work out-of-the-box if installed with miniconda.

The anaconda_nbservice will run a Jupyter notebook server as a runit service:

  anaconda_nbservice 'notebook-server' do
    # listen on all interfaces; there will be a warning since security is
    # disabled
    ip '*'
    port '8888'

    install_dir '/opt/jupyter/server'

    service_action [ :enable, :start ]

The standard configuration should be good enough, but you might need to write your own run service template:

  anaconda_nbservice 'server-with-custom-template' do
    user jupyter_user
    group jupyter_group

    install_dir install_dir

    template_cookbook 'your_cookbook'
    # note that if your template name is TEMPLATE, then this value should be
    # 'TEMPLATE", but the file should be 'sv-TEMPLATE-run.erb'
    run_template_name 'your_template_name'

    service_action [ :enable, :start ]

Developer setup, config, and tests

See []( for details.

Releases and issues

Standard stuff:



Author:: Matt Chu (

Dependent cookbooks

tar >= 0.0.0
bzip2 >= 0.0.0
runit >= 0.0.0
apt >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.



This is a backwards-INCOMPATIBLE release

  • Catch up with ipython -> jupyter rebranding: renamed everything to juptyer. This includes directories, attributes, and other backwards-incompatible changes.
  • More fixes to release process: don't include unnecessary files during berkshelf vendoring and release
  • Vagrant and notebook server fixes
    • you can use attributes to set the notebook server's security token. Be careful with this config! It is disabled in the quickstart Vagrant setup for convenience, and remains enabled by default.
  • Foodcritic fixes; resolves:
    • FC017: LWRP does not notify when updated: anaconda/providers/nbservice.rb:21
    • FC017: LWRP does not notify when updated: anaconda/providers/package.rb:21
    • FC017: LWRP does not notify when updated: anaconda/providers/package.rb:58
    • FC059: LWRP provider does not declare use_inline_resources: anaconda/providers/nbservice.rb:1
    • FC059: LWRP provider does not declare use_inline_resources: anaconda/providers/package.rb:1
    • FC048: Prefer Mixlib::ShellOut: ./providers/nbservice.rb:12
    • FC048: Prefer Mixlib::ShellOut: ./providers/package.rb:12


This cookbook is now up for adoption! See for details.

  • Post release cleanup:
    • release script and better document release process
    • remove references to Chef DK
  • (WIP!) Update Vagrant instructions:
    • Use Vagrant 2.0
    • Update image to use Ubuntu 16.04 LTS (xenial), from 14.04 LTS
  • Lint/Quality
    • Added
    • Added, and move content from to that file
    • Remove vim swapfiles from release, because chefignore doesn't seem to do shit.
  • Added checksums for new 5.0 Anaconda installers


Many, many changes and fixes to support both the latest Chef version and the latest Anaconda versions.

Adds support for Anaconda 4.4.0 and 5.0.1! 5.0.1 is now the default.

Cookbook changes:

  • Adds a system_path attribute, for adding Anaconda's bin path to PATH.

Chef changes:

  • Dot notation attributes (eg node.attr1.prop1) have been deprecated and is now an error; converted everything to hash/bracket notation (eg node['attr1']['prop1']).
  • Cleanups to metadata.rb.

Updated tested list of OSes

The list of tested OSes has been refined to the latest and penultimate (major) stable versions. Note that just because an OS is not on the tested list does not mean it won't work, it just means it is not part of the official test suite. My experience has been it generally will.

  • Ubuntu:
    • Removed tests for: 12.04, 15.04
    • Added tests for: 16.04
  • Debian:
    • Removed tests for: 7.8, 8.1
    • Added tests for: 8.9, 9.1
  • CentOS:
    • Removed tests for: 5.11, 6.6, 7.1
    • Added tests for: 6.9, 7.4
  • Red Hat: completed removed from test suite, in favor of CentOS only

Development, fixes:

  • Gemfile now annotated with rvm metadata for ruby version and gemset.
  • Fixed vagrant-trigger to correctly populate /var/chef/cache on provision.
  • Fixed bad call to Chef::Log with fatal.


First official 0.6.x release; see 0.6.0 changelog for details.

Note that this reverts the release process back to using Chef 11.x/ChefDK 0.3.6 because of

0.6.1 (broken, untagged release thanks to ChefDK)

Do not use.

0.6.0 (unreleased thanks to ChefDK)

This is a backwards-INCOMPATIBLE release

API, cookbook changes:

  • Refactored attributes to be cleaner and more readable
  • The user and group are now created if they don't exist, and by default are installed under anaconda/anaconda
  • New attributes for configuring notebook server
  • The OS architecture (x86 versus x86_64) is now autodetected by default

Platform, support changes:

  • Added support for Anaconda 2.3 (all pythons and all architectures)
  • Removed support for all Anacondas < 2.2.0
  • updated metadata.rb 'supports' tags (hopefully this doesn't break anything)

Tools changes:

  • Migrated to chefdk 0.8.1
    • upgraded gems
    • updated chefspec
    • updated documentation
    • removed rbenv/rvm files

Testing changes:

  • Moved to kitchen-docker for Docker-based testing, which is much much much faster
  • Updated supported (tested) platforms:
    • ubuntu:
    • removed: 12.10, 13.04, 13.10
    • added: 15.04
    • debian:
    • removed: 6.0.5
    • added: 7.8, 8.1 (7.9 and 8.2 not in fauxhai yet)
    • centos:
    • removed: 5.8, 6.0, 6.3
    • added: 5.11, 6.6, 7.1.1503
    • redhat (chefspec only, no kitchen testing):
    • removed: 5.8, 6.3
    • added: 5.9, 6.6, 7.1.1503



  • Upgraded to Anaconda 2.2.0 from 2.0.1
    • Includes support for Anaconda 2.1.0
  • Added support for Miniconda
  • Upgraded Vagrantfile:
    • Upgraded Chef from 11.16+ to 12+ to match Kitchen tests
    • Upgraded OS from 12.04 to 14.04


Backwards-compatible fix for issue when using both the python cookbook and this one. Issue:


Unintended release, thanks to Chef Supermarket's crappiness.


New resource 'anaconda_nbservice', for running an IPython notebook server. Somewhat experimental, it's fairly basic but usable.


Hotfix release:


Major cleanup and basic usability fixes (read: almost not sure why it worked before, if it even did):

  • (core, breaking) Renamed anaconda::shell-conveniences to anaconda::shell_conveniences
  • (core, breaking) No longer uses the python cookbook; this caused problems after anaconda was installed
  • (core) shell_conveniences now installs into /etc/profile.d, so it is automatically sourced by login shells
  • (core) Ubuntu 14.04 is now a supported (and fully tested) platform
  • (core) Ubuntu 14.04 is now the default platform used in the sample Vagrantfile
  • (core) Vagrantfile now correctly installs Anaconda, like the README said it was supposed to
  • (docs) various readme updates
  • (testing) Complete coverage of all resources in chefspec
  • (testing) Removed Ubuntu 12.10 and 13.04 from kitchen testing; there's something wrong with apt-get on these images. It appears to be something about the apt keys, but they're just removed from testing for now.


Bugfix release:

  • Fixes related to install script and permissions (#5). Courtesy @mwalton236


New resource: anaconda_package, for installing and removing packages via conda


Rewrote all project history


Fix incorrect checksums for Anaconda 2.0.1


Feature improvments:

  • updated the default installation to Anaconda 2.0.1, from 1.9.2


  • minor cibuild improvement to ensure clean tests
  • minor code changes to support updated toolchain
  • removed Chef Development Kit recommendation after experimenting with it

Collaborator Number Metric

0.7.2 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric

0.7.2 passed this metric

Foodcritic Metric

0.7.2 passed this metric

No Binaries Metric

0.7.2 passed this metric

Publish Metric

0.7.2 failed this metric

anaconda is up for adoption

Supported Platforms Metric

0.7.2 passed this metric

Testing File Metric

0.7.2 passed this metric

Version Tag Metric

0.7.2 passed this metric