Skip to content

registry job from docker-registry/3.2.1

Docker Registry v2 API

Github source: 080dc0ba or master branch

Properties

docker

cache

host

IP address of the redis cache host

password

Password to access the cache host

pool

Configure the behavior of the Redis connection pool.

Default
  idletimeout: 300s
  maxactive: 64
  maxidle: 16
port

Port address of the cache host

Default
6379

mirror

host

Enables a registry to be configured as a pull through cache to the official Docker Hub. See mirror for more information

Example
https://registry-1.docker.io
password

Docker registry password

username

Docker registry username

registry

bind

What address to bind the Docker Registry v2 API

cookie

A secret cookie used to sign state against tampering.

debug

Debug endpoint can be used for monitoring registry metrics and health, as well as profiling

Example
localhost:5001
endpoint

Externally-reachable address for the registry, as a fully qualified URL. If present, it is used when creating generated URLs. Otherwise, these URLs are derived from client requests

Example
https://myregistryaddress.org:5000
health_cache_enabled

In case of cache is defined, enables a periodic health check on the redis host and port

Default
true
health_storagedriver_enabled

Enable periodic health check on the storage driver’s backend storage

Default
true
loglevel

Sets the sensitivity of logging output. Permitted values are error, warn, info and debug

Default
info
ofiles

Open files (ulimit)

Default
10000
port

What port to run the Docker Registry v2 API on

Default
5000
reporting

Configures error and metrics reporting tools. At the moment only two services are supported, New Relic and Bugsnag

Example
newrelic:
  licensekey: newreliclicensekey
  name: newrelicname
root

Path (on-disk, locally) where the Docker registry should store its data (filesystem storage backend)

Default
/var/vcap/store/registry
ssl
cert

PEM-encoded SSL certificate for HTTPS registry operation

key

PEM-encoded private key for HTTPS registry operation

storage

Defines which storage backend is in use, otherwise filesystem backend will be used

Example
s3:
  accesskey: awsaccesskey
  bucket: bucketname
  chunksize: 5.24288e+06
  encrypt: true
  keyid: mykeyid
  region: us-west-1
  regionendpoint: http://myobjects.local
  rootdirectory: /s3/object/name/prefix
  secretkey: awssecretkey
  secure: true
  v4auth: true
storage_delete

Enable the deletion of image blobs and manifests by digest

Default
false
storage_disable_redirect

Route all data through the Registry, or redirect the client to the backend in order to download from there

Default
false
storage_maintenance

Maintenance jobs for storage, upload purging and read-only mode are the only functions available

Default
  readonly:
    enabled: false
  uploadpurging:
    age: 168h
    dryrun: false
    enabled: true
    interval: 24h

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/registry/ directory (learn more).

  • bin/ctl (from bin/ctl)
  • bin/monit_debugger (from bin/monit_debugger)
  • config/registry.conf (from config/registry.conf)
  • data/properties.sh (from data/properties.sh.erb)
  • helpers/ctl_setup.sh (from helpers/ctl_setup.sh)
  • helpers/ctl_utils.sh (from helpers/ctl_utils.sh)
  • tls/cert.pem (from tls/cert.pem)
  • tls/key.pem (from tls/key.pem)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.