Inmemory: # This driver takes no parametersĪuthorization: version: 0.1ĭomain: domain name for Openstack Identity v3 APIĭomainid: domain id for Openstack Identity v3 APIĮncrypt: optional data encryption setting Option before finalizing your configuration. Read the detailed reference information about each Some options in the listĪre mutually exclusive. These are all configuration options for the registry. $ docker run -d -p 5000:5000 -restart =always -name registry \ -v ` pwd `/config.yml:/etc/docker/registry/config.yml \Īs a starting point. Typically, create a new configuration file from scratch,named config.yml, then YAML configuration file by mounting it as a volume in the container. Having issues overriding keys from the environment, you can specify an alternate If the default configuration is not a sound basis for your usage, or if you are With environment variables is not recommended. Note: Create a base configuration file with environment variables that canīe configured to tweak individual values. This variable overrides the /var/lib/registry value to the /somewhere To override this value, set an environment variable like this: REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/somewhere For example, you canĬonfigure the rootdirectory of the filesystem storage backend: storage:
REGISTRY_variable where variable is the name of the configuration optionĪnd the _ (underscore) represents indention levels. To override a configuration option, create an environment variable named To your docker run stanza or from within a Dockerfile using the ENV
Specify a configuration variable from the environment by passing -e arguments In a typical setup where you run your Registry from the official image, you can While itĬomes with sane default values out of the box, you should review it exhaustivelyīefore moving your systems to production.
The Registry configuration is based on a YAML file, detailed below.
0 kommentar(er)
