Forge Home

docker_distribution

installs and configures docker registry

8,926 downloads

6,866 latest version

4.3 quality score

Version information

  • 3.4.0 (latest)
  • 3.3.0
  • 3.2.1
  • 3.1.0
  • 3.0.0
released Feb 21st 2017
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet >=3.4.0 <5.0.0
  • , , , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'cristifalcas-docker_distribution', '3.4.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add cristifalcas-docker_distribution
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install cristifalcas-docker_distribution --version 3.4.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

cristifalcas/docker_distribution — version 3.4.0 Feb 21st 2017

docker_distribution

Build Status

Puppet module for installing, configuring and managing Docker Registry 2.0

Support

This module is currently only for RedHat clones 6.x, 7.x and OpenSuSE:

The Docker toolset to pack, ship, store, and deliver content.

Usage:

      include docker_distribution

Use tls (it will use puppet certificates) and enable email hooks:

  class { '::docker_distribution':
    log_fields               => {
      service     => 'registry',
      environment => 'production'
    }
    ,
    log_hooks_mail_disabled  => false,
    log_hooks_mail_levels    => ['panic', 'error'],
    log_hooks_mail_to        => 'docker_distribution@company.com',
    filesystem_rootdirectory => '/srv/registry',
    http_addr                => ':1443',
    http_tls                 => true,
  }

Start from a container:

      class { '::docker_distribution':
        manage_as                    => 'container',
        # configuration
        log_fields                   => {
          service     => 'registry',
          environment => 'production',
        },
        log_hooks_mail_disabled      => false,
        log_hooks_mail_levels        => ['panic'],
        log_hooks_mail_to            => 'cloud@company.com',
        log_hooks_mail_smtp_addr     => 'localhost:25',
        log_hooks_mail_smtp_insecure => true,
        filesystem_rootdirectory     => '/srv/registry',
        http_addr                    => ':1443',
        http_tls                     => true,
        storage_delete               => true,
      }

Journald forward:

The class support a parameter called journald_forward_enable.

This was added because of the PIPE signal that is sent to go programs when systemd-journald dies.

For more information read here: https://github.com/projectatomic/forward-journald

Usage:

  include ::forward_journald
  Class['forward_journald'] -> Class['docker_distribution']