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

Select Status


resolvconf (15) Versions 1.0.0

Installs/Configures resolvconf

cookbook 'resolvconf', '~> 1.0.0', :supermarket
cookbook 'resolvconf', '~> 1.0.0'
knife supermarket install resolvconf
knife supermarket download resolvconf
Quality 17%

resolvconf Cookbook

This cookbook maintains /etc/resolv.conf using the resolvconf package, which is installed by default on Debian/Ubuntu.


A system that supports resolvconf.

  • Ubuntu >= 12.04
  • Debian >= 6.0

Furthermore you need to add the following line to your metadata.rb

depends 'resolvconf'


This section describes the supported attributes, as well as their default settings.

Use the following attributes to specify your nameserver(s) to use, the search domain(s) and additional options.
Each attribute supports strings, as well as arrays with multiple elements.

node['resolvconf']['nameserver'] = %w( # Set nameserver(s) to use
node['resolvconf']['search'] = node['domain'] # Set domains to search
node['resolvconf']['options'] = [] # Set options
node['resolvconf']['sortlist'] = [''] # Default is empty

These attributes specify strings that are included in /etc/resolv.conf at head/body/tail.

node['resolvconf']['head'] = [
  '# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)',
node['resolvconf']['base'] = []
node['resolvconf']['tail'] = []

By default, the recipe removes any dns-* configuration lines from /etc/network/interfaces,
as they might interferre with the configured settings.

node['resolvconf']['clear-dns-from-interfaces'] = true

You can force the resolvconf cookbook to wipe old entries from the runtime directories. Use this if
you have trouble with old resolv.conf entries ending up in your configuration.
This is not enabled by default, as it removes the dynamic capabilities of resolvconf which enable
applications to change nameserver settings on the fly.

node['resolvconf']['wipe-runtime-directory'] = false

You can set a list of interfaces that you want to inherit the dns settings from. It creates the
interface-order file /etc/resolvconf/interface-order and builds it from the list.
This enables you to control which additional dns servers if any are added from which interfaces.
node['resolvconf']['interface-order'] = [



The LWRP basically supports all options that can be set via attributes, and uses the same defaults.
It will do the following

  • It will create the necessary files in /etc/resolvconf/resolv.conf.d/
  • Remove dns-* lines from /etc/network/interfaces (unless clear_dns_form_interfaces is specified)
  • Run 'resolvconf -u'

Before using the provider, you probably want to ensure that the resolvconf package is installed.

include_recipe 'resolvconf::install'


resolvconf 'default'
resolvconf 'custom' do
  nameserver ''
  search     ''
  options    'rotate'
  sortlist   'mysortlist'

  head       "# Don't touch this configuration file!"
  base       "# Will be added after nameserver, search, options config items"
  tail       "# This goes to the end of the file."

  # do not touch my interface configuration plz!
  clear_dns_from_interfaces false



Installs the resolvconf package.


Includes resolvconf::install, then configures the node using the specified attributes / defaults.


Contributions are very welcome!

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write you change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License and Authors

Authors: Chris Aumann

License: GPLv3

CHANGELOG for resolvconf

This file is used to list changes made in each version of resolvconf.


  • Remove default nameservers. Make sure you set them before migrating to this version! See this issue for details.


  • Remove support for Ubuntu 10.04 (Official support ended Q1 2015)


  • Add default interface names for Ubuntu Xenial 16.04


  • Add custom matcher for ChefSpec


  • Use use_inline_resources to fix a bug with resolvconf -u not being immediately called.


  • Allow wipe_runtime_directory to be specified as resource attribute. Defaults to node attribute.


  • Add support for interface-order
  • Make sure /etc/resolv.conf is a symlink to /run/resolvconf/resolv.conf


  • /run/resolvconf/interface/ is wiped only when node['resolvconf']['wipe-runtime-directory'] is set to true. Defaults to false. This resolves issues with applications using the dynamic nameserver configuration capabilities of resolvconf.


  • Include a workaround for Ubuntu-10.04 (Debian bug #642222)


  • Remove support for the domain attribute, as resolvconf ignores it. Use search attribute instead.


  • Add support for sortlist and domain settings


  • Remove a workaround for force_unlink, fix was merged in Chef 11.12.0
  • Clear /run/resolvconf/interface/ directory before updating /etc/resolv.conf, to prevent deprecated entries from ending up in the file



  • Remove potential symlinks before deploying new configuration


  • Add tests (using kitchen, see
  • Run resolvconf --enable-updates before resolvconf -u (when supported)
  • Use Chef::Util::FileEdit instead of execute() and sed


  • Initial release of resolvconf

Collaborator Number Metric

1.0.0 failed this metric

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

Contributing File Metric

1.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Foodcritic Metric

1.0.0 failed this metric

FC064: Ensure issues_url is set in metadata: resolvconf/metadata.rb:1
FC065: Ensure source_url is set in metadata: resolvconf/metadata.rb:1
FC066: Ensure chef_version is set in metadata: resolvconf/metadata.rb:1
FC069: Ensure standardized license defined in metadata: resolvconf/metadata.rb:1
FC072: Metadata should not contain "attribute" keyword: resolvconf/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric

1.0.0 passed this metric

Testing File Metric

1.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Version Tag Metric

1.0.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must include a tag that matches this cookbook version number