Customizing registry

The following settings are tunable for the Registry component.

Dependencies

Requires: cache, store-gateway

Required by: builder, controller

Considerations: none

Settings set by registry

The following etcd keys are set by the registry component, typically in its /bin/boot script.

setting description
/deis/registry/bucketName store component bucket used for registry image layers (default: registry)
/deis/registry/host IP address of the host running registry
/deis/registry/port port used by the registry service (default: 5000)
/deis/registry/protocol protocol for registry (default: http)

Settings used by registry

The following etcd keys are used by the registry component.

setting description
/deis/cache/host host of the cache component (set by cache)
/deis/cache/port port of the cache component (set by cache)
/deis/store/gateway/accessKey S3 API access used to access store-gateway (set by store-gateway)
/deis/store/gateway/host host of the store-gateway component (set by store-gateway)
/deis/store/gateway/port port of the store-gateway component (set by store-gateway)
/deis/store/gateway/secretKey S3 API secret key used to access store-gateway (set by store-gateway)

The Deis registry component inherits from the Docker registry container, so additional configuration options can be supplied. For a full explanation of these settings, see the Docker registry README.

Using a custom registry image

You can use a custom Docker image for the registry component instead of the image supplied with Deis:

$ deisctl config registry set image=myaccount/myimage:latest

This will pull the image from the public Docker registry. You can also pull from a private registry:

$ deisctl config registry set image=registry.mydomain.org:5000/myaccount/myimage:latest

Be sure that your custom image functions in the same way as the stock registry image shipped with Deis. Specifically, ensure that it sets and reads appropriate etcd keys.