Container Registry

Each VPC includes a private Docker registry powered by Harbor. Push your images here and deploy them to services.

Registry credentials

Find your registry credentials in the VPC's Registry section. The credentials are also stored as a Kubernetes secret (harbor-registry) with these keys:

Pushing images

# Log in
docker login registry.smll.io
# Enter your registry username and password when prompted

# Tag your image with the VPC project name
docker tag myapp:latest registry.smll.io/vpc-abc12345/myapp:v1.0.0

# Push
docker push registry.smll.io/vpc-abc12345/myapp:v1.0.0

Pulling images

Services in your VPC automatically have access to pull images — no additional configuration needed. The pull secret is injected into every service deployment.

To pull manually:

docker pull registry.smll.io/vpc-abc12345/myapp:v1.0.0

You can also pull by digest for immutable references:

docker pull registry.smll.io/vpc-abc12345/myapp@sha256:abc123...

Vulnerability scanning

Every image pushed to the registry is automatically scanned for vulnerabilities using Trivy. View scan results from the registry dashboard:

• CVE ID — the vulnerability identifier
• Package — the affected package
• Severity — critical, high, medium, or low
• Fix version — the version that resolves the vulnerability

Image tagging best practices

• Use semantic versioning — tag images with v1.0.0, v1.0.1, etc. for clear release tracking
• Avoid latest in production — use explicit version tags so deployments are reproducible
• Use git SHA tags for CI/CD — e.g. myapp:abc123f for traceability back to source
• Clean up old images — delete unused tags to save registry storage

Registry metrics

The dashboard shows:

• Total repositories — number of image repositories
• Total artifacts — number of image tags/digests
• Total pulls — cumulative pull count
• Storage used — total registry storage

Related

• Deploying Services — deploy images from your registry
• Secrets — registry credentials are auto-generated as secrets