Skip to main content
Version: 0.0.14

Container Registry

Container Registry provides a private Docker container registry for storing and managing container images in Aruba Cloud.

Command Syntax​

acloud container containerregistry <command> [flags] [arguments]

Available Commands​

create​

Create a new container registry.

Syntax:

acloud container containerregistry create [flags]

Required Flags:

  • --name <string> - Name for the container registry
  • --region <string> - Region code (e.g., ITBG-Bergamo)
  • --public-ip-uri <string> - Public IP URI (e.g., /projects/{project-id}/providers/Aruba.Network/elasticIps/{elasticip-id})
  • --vpc-uri <string> - VPC URI (e.g., /projects/{project-id}/providers/Aruba.Network/vpcs/{vpc-id})
  • --subnet-uri <string> - Subnet URI (e.g., /projects/{project-id}/providers/Aruba.Network/subnets/{subnet-id})
  • --security-group-uri <string> - Security group URI
  • --block-storage-uri <string> - Block storage URI

Optional Flags:

  • --project-id <string> - Project ID (uses context if not specified)
  • --tags <stringSlice> - Tags (comma-separated)
  • --billing-period <string> - Billing period: Hour, Month, Year (optional)
  • --admin-username <string> - Administrator username (optional)
  • --concurrent-users <string> - Number of concurrent users (optional)

Example:

acloud container containerregistry create \
  --name "my-registry" \
  --region "ITBG-Bergamo" \
  --public-ip-uri "/projects/{project-id}/providers/Aruba.Network/elasticIps/{elasticip-id}" \
  --vpc-uri "/projects/{project-id}/providers/Aruba.Network/vpcs/{vpc-id}" \
  --subnet-uri "/projects/{project-id}/providers/Aruba.Network/subnets/{subnet-id}" \
  --security-group-uri "/projects/{project-id}/providers/Aruba.Network/securityGroups/{sg-id}" \
  --block-storage-uri "/projects/{project-id}/providers/Aruba.Storage/volumes/{volume-id}" \
  --billing-period "Month" \
  --tags "production,registry"

list​

List all container registries in the project.

Syntax:

acloud container containerregistry list [flags]

Optional Flags:

  • --project-id <string> - Project ID (uses context if not specified)

Example:

acloud container containerregistry list

Output: The command displays a table with the following columns:

  • NAME
  • ID
  • REGION
  • STATUS

get​

Get detailed information about a specific container registry.

Syntax:

acloud container containerregistry get <registry-id> [flags]

Arguments:

  • <registry-id> - The ID of the container registry

Optional Flags:

  • --project-id <string> - Project ID (uses context if not specified)
  • --verbose - Show detailed JSON output

Example:

acloud container containerregistry get 69495ef64d0cdc87949b71ec

Output: The command displays detailed information including:

  • ID and URI
  • Name and region
  • Public IP, VPC, Subnet, Security Group, Block Storage
  • Billing plan
  • Admin user (if configured)
  • Concurrent users
  • Status
  • Creation date and creator
  • Tags

update​

Update a container registry's properties (name, tags, billing period, concurrent users).

Syntax:

acloud container containerregistry update <registry-id> [flags]

Arguments:

  • <registry-id> - The ID of the container registry

Optional Flags:

  • --project-id <string> - Project ID (uses context if not specified)
  • --name <string> - New name for the container registry
  • --tags <stringSlice> - New tags (comma-separated)
  • --billing-period <string> - Billing period: Hour, Month, Year
  • --concurrent-users <string> - Number of concurrent users

Example:

acloud container containerregistry update 69495ef64d0cdc87949b71ec \
  --name "my-registry-updated" \
  --tags "production,registry,updated" \
  --billing-period "Year" \
  --concurrent-users 10

Note: At least one of --name, --tags, --billing-period, or --concurrent-users must be provided.

delete​

Delete a container registry.

Syntax:

acloud container containerregistry delete <registry-id> [flags]

Arguments:

  • <registry-id> - The ID of the container registry

Optional Flags:

  • --project-id <string> - Project ID (uses context if not specified)
  • --yes, -y - Skip confirmation prompt

Example:

acloud container containerregistry delete 69495ef64d0cdc87949b71ec --yes

Auto-completion​

The CLI provides auto-completion for container registry IDs:

acloud container containerregistry get <TAB>
acloud container containerregistry update <TAB>
acloud container containerregistry delete <TAB>

Common Workflows​

Creating a Container Registry​

  1. Ensure required resources exist:

    • Public IP (Elastic IP)
    • VPC
    • Subnet
    • Security Group
    • Block Storage

  2. Create the container registry:

    acloud container containerregistry create \
      --name "my-registry" \
      --region "ITBG-Bergamo" \
      --public-ip-uri "/projects/{project-id}/providers/Aruba.Network/elasticIps/{elasticip-id}" \
      --vpc-uri "/projects/{project-id}/providers/Aruba.Network/vpcs/{vpc-id}" \
      --subnet-uri "/projects/{project-id}/providers/Aruba.Network/subnets/{subnet-id}" \
      --security-group-uri "/projects/{project-id}/providers/Aruba.Network/securityGroups/{sg-id}" \
      --block-storage-uri "/projects/{project-id}/providers/Aruba.Storage/volumes/{volume-id}" \
      --billing-period "Month"

  3. Wait for the registry to be ready and check status:

    acloud container containerregistry get <registry-id>

Updating Registry Metadata​

# Update registry name and tags
acloud container containerregistry update <registry-id> \
  --name "new-name" \
  --tags "production,updated"

# Update billing period
acloud container containerregistry update <registry-id> \
  --billing-period "Year"

# Update concurrent users
acloud container containerregistry update <registry-id> \
  --concurrent-users 20

Listing and Filtering Registries​

# List all registries
acloud container containerregistry list

# Use grep to filter by name or tags
acloud container containerregistry list | grep "production"

Best Practices​

  • Naming: Use descriptive names that indicate the registry's purpose (e.g., prod-registry, dev-registry)
  • Tags: Use tags to organize registries by environment, project, or team
  • Billing Period: Choose appropriate billing periods based on expected usage
  • Concurrent Users: Set concurrent users based on your team size and usage patterns
  • Security: Ensure security groups are properly configured to restrict access
  • Storage: Monitor block storage usage and expand as needed
  • Cleanup: Delete unused registries to avoid unnecessary costs