Files

Mark Goddard 3b1a8a6a00 Don't pull registry image from private registry

This avoids a potential circular dependency where the registry is the
source of its own image.

Also fixes up the image building documentation about the default value
of kolla_docker_registry.

Change-Id: Ia30173abf185329098ace621baf0ad1be75c0b74
Story: 2004820
Task: 29345

2019-02-05 12:05:33 +00:00

defaults

Don't pull registry image from private registry

2019-02-05 12:05:33 +00:00

tasks

Merge "use include_tasks and import_playbook instead of include"

2019-02-04 13:33:30 +00:00

README.md

Update python docker package requirement note in role READMEs

2017-12-13 17:03:54 +00:00

README.md

Docker Registry

This role can be used to configure a Docker registry running in a Docker container.

Requirements

The host executing the role has the following requirements:

Docker engine
Python docker >= 2.0.0

Role Variables

docker_registry_enabled: Whether the Docker registry is enabled. Defaults to true. docker_registry_namespace: Docker image namespace. Defaults to library. docker_registry_image: Docker image name. docker_registry_tag: Docker image tag. Defaults to latest. docker_registry_image_full: Full docker image specification. docker_registry_restart_policy: Docker restart policy for docker_registry container. Defaults to unless-stopped. docker_registry_restart_retries: Number of Docker restarts. Defaults to 10.

Dependencies

None

Example Playbook

The following playbook configures a Docker registry.

---
- hosts: docker-registry
  roles:
    - role: stackhpc.docker-registry

Author Information

Mark Goddard (mark@stackhpc.com)