blossom container_registry:create
Create a container registry
Usage
blossom container_registry:create [--data DATA]
Flags
| Flag | Description |
|---|---|
--data, -d |
YAML or JSON data, a path to a data file, or an HTTP(S) URL |
Examples:
blossom container_registry:init
blossom container_registry:create --data container_registry.yml
Creates a container registry connection in the current Blossom Account.
Run blossom container_registry:types to discover the current registry keys
and requirements.
Supported registry_type values:
| registry_type | Provider | Credentials |
|---|---|---|
dockerhub |
Docker Hub | username, password |
ghcr |
GitHub Container Registry | password personal access token |
gitlab |
GitLab Container Registry | username, password or token |
quay |
Quay.io | username, password |
ecr |
Amazon ECR | cloud_provider_id, region |
gcr |
Google Container Registry | cloud_provider_id |
acr |
Azure Container Registry | cloud_provider_id, url |
custom |
Custom Registry | url, optional username, optional password |
Docker Hub:
container_registry:
name: dockerhub-production
registry_type: dockerhub
username: my-dockerhub-user
password: ${DOCKERHUB_TOKEN}
GitHub Container Registry:
container_registry:
name: github-packages
registry_type: ghcr
password: ${GITHUB_PACKAGES_TOKEN}
Amazon ECR:
container_registry:
name: aws-ecr-production
registry_type: ecr
cloud_provider_id: cloud_provider-100
region: us-east-1
Azure Container Registry:
container_registry:
name: azure-acr-production
registry_type: acr
cloud_provider_id: cloud_provider-100
url: myregistry.azurecr.io
Custom Registry:
container_registry:
name: internal-registry
registry_type: custom
url: registry.example.com
username: ${REGISTRY_USERNAME}
password: ${REGISTRY_PASSWORD}
Cloud-backed registry types require a matching cloud provider connection:
blossom cloud_provider:list
Local files and inline data support $VAR and ${VAR} substitution from
.env, BLOSSOM_VARS_FILE, and the process environment. See
blossom help:data.