ConfigurationRegistriesGCR
GCR (Google Container Registry)
The gcr registry lets you configure GCR integration. GCR was shut down by Google in 2025 — consider using GAR instead.
Google Container Registry was shut down in 2025. All gcr.io traffic is now transparently served by Google Artifact Registry (GAR). The drydock GCR provider still functions because gcr.io endpoints redirect to Artifact Registry, but new projects should use the GAR provider instead.
The gcr registry lets you configure GCR integration.
Variables
| Env var | Required | Description | Supported values | Default value when missing |
|---|---|---|---|---|
DD_REGISTRY_GCR_{REGISTRY_NAME}_CLIENTEMAIL | ⚪ | Service Account Client Email (required for private images access) | See Service Account credentials | |
DD_REGISTRY_GCR_{REGISTRY_NAME}_PRIVATEKEY | ⚪ | Service Account Private Key (required for private images access) | See Service Account credentials |
Examples
Configure for authenticated access
services:
drydock:
image: codeswhat/drydock
...
environment:
- DD_REGISTRY_GCR_PRIVATE_CLIENTEMAIL=johndoe@mysuperproject.iam.gserviceaccount.com
- DD_REGISTRY_GCR_PRIVATE_PRIVATEKEY=-----BEGIN PRIVATE KEY-----xxxxxxxxxxx\n-----END PRIVATE KEY-----\n docker run \
-e DD_REGISTRY_GCR_PRIVATE_CLIENTEMAIL="johndoe@mysuperproject.iam.gserviceaccount.com" \
-e DD_REGISTRY_GCR_PRIVATE_PRIVATEKEY="-----BEGIN PRIVATE KEY-----xxxxxxxxxxx\n-----END PRIVATE KEY-----\n" \
...
codeswhat/drydock