ConfigurationRegistriesOCIR
OCIR (Oracle Cloud Infrastructure Registry)
The ocir registry lets you configure Oracle Cloud Infrastructure Registry integration.
The ocir registry lets you configure OCIR integration.
Drydock automatically detects the bare ocir.io hostname and subdomains such as iad.ocir.io.
Variables
| Env var | Required | Description | Supported values | Default value when missing |
|---|---|---|---|---|
DD_REGISTRY_OCIR_{REGISTRY_NAME}_LOGIN | ⚪ | OCI username (tenancy-namespace/user@example.com for default-domain users; tenancy-namespace/identity-domain/user@example.com for federated or non-default-domain users) | DD_REGISTRY_OCIR_{REGISTRY_NAME}_PASSWORD must be defined | |
DD_REGISTRY_OCIR_{REGISTRY_NAME}_PASSWORD | ⚪ | Auth token | DD_REGISTRY_OCIR_{REGISTRY_NAME}_LOGIN must be defined | |
DD_REGISTRY_OCIR_{REGISTRY_NAME}_AUTH | ⚪ | Base64-encoded login:password string | DD_REGISTRY_OCIR_{REGISTRY_NAME}_LOGIN/PASSWORD must not be defined |
Examples
Configure with login and password
services:
drydock:
image: codeswhat/drydock
...
environment:
- DD_REGISTRY_OCIR_PRIVATE_LOGIN=tenancy/oracleidentitycloudservice/user@example.com
- DD_REGISTRY_OCIR_PRIVATE_PASSWORD=xxxxxdocker run \
-e "DD_REGISTRY_OCIR_PRIVATE_LOGIN=tenancy/oracleidentitycloudservice/user@example.com" \
-e "DD_REGISTRY_OCIR_PRIVATE_PASSWORD=xxxxx" \
...
codeswhat/drydockConfigure with base64 auth
services:
drydock:
image: codeswhat/drydock
...
environment:
- DD_REGISTRY_OCIR_PRIVATE_AUTH=dGVuYW5jeS9vcmFjbGVpZGVudGl0eWNsb3Vkc2VydmljZS91c2VyQGV4YW1wbGUuY29tOnh4eHh4docker run \
-e "DD_REGISTRY_OCIR_PRIVATE_AUTH=dGVuYW5jeS9vcmFjbGVpZGVudGl0eWNsb3Vkc2VydmljZS91c2VyQGV4YW1wbGUuY29tOnh4eHh4" \
...
codeswhat/drydockHow to create an Auth Token on Oracle Cloud
Go to your OCI Console and open the Auth Tokens page
Navigate to Identity & Security > Users > Your User > Auth Tokens.
Generate token
Click Generate Token, give it a description, and copy the generated token value.
Use your full OCI username (e.g. tenancy/oracleidentitycloudservice/user@example.com) as the login and the generated token as the password.