Global Registries File

The enterprise expansion pack provides support for global registry credentials, sourced from a yaml file on your server. You should mount the credentials file into your container and specify the path to the file in your configuration.

Example server configuration:

    image: drone/drone:0.8

      - 80:8000
      - /var/lib/drone:/var/lib/drone/
+     - /etc/drone-registry.yml:/etc/drone-registry.yml
    restart: always
+     DRONE_GLOBAL_REGISTRY=/etc/drone-registry.yml

Example registry credentials file:

- address:
  username: octocat
  password: correct-horse-batter-staple
- address:
  username: _json_key
  password: |
      "private_key_id": "...",
      "private_key": "...",
      "client_email": "...",
      "client_id": "...",
      "type": "..."

Elastic Container Registry (ECR)

The global registry file supports elastic container registries. Temporary authentication credentials are automatically generated and refreshed using the GetAuthorizationToken endpoint. Note that you must provide your aws access key and secret, and configure the appropriate IAM roles.

Example registry credentials for an ECR repository:

- address:
  aws_access_key_id: a50d28f4dd477bc184fbd10b376de753
  aws_secret_access_key: bc5785d3ece6a9cdefa42eb99b58986f9095ff1c

Restricting Access

Currently, global registry credentials do not support any attribute-based usage restriction (repo, images, events).

This is because registry credentials are internal-only to Drone, and unlike secrets, are never exposed to the build.

Is there a mistake on this page? Please let us know or edit this page.