Container Registry
Manage Repositories
View and manage your container image repositories
Manage Repositories
Learn how to view, organize, and manage your container image repositories in DCR.
Viewing Repositories
Via Console
- Log in to the Nexqloud Console
- Navigate to Container → DCR Container Registry
- Click on your registry name
- View the Repositories tab
Each repository displays:
- Repository name
- Number of tags
- Last push date
- Image size
Via CLI
List repositories using the Docker/Podman CLI:
# This requires registry API access
curl -u username:password https://dcr.nexqloud.io/v2/your-registry-name/_catalog
Repository Structure
Repositories are automatically created when you push an image:
docker push dcr.nexqloud.io/your-registry-name/repository-name:tag
Repository naming best practices:
- Use lowercase letters and hyphens
- Group related images (e.g.,
frontend/web,backend/api) - Include project or service names
Viewing Image Tags
In the Console
- Click on a repository name
- View all tags for that repository
- See tag details including:
- Tag name
- Digest (SHA256)
- Size
- Push date
Using Docker CLI
List tags for a specific repository:
# View all tags
docker images dcr.nexqloud.io/your-registry-name/repository-name
# Pull specific tag
docker pull dcr.nexqloud.io/your-registry-name/repository-name:tag
Organizing Repositories
Hierarchical Structure
Organize repositories using path-like names:
dcr.nexqloud.io/your-registry-name/
├── frontend/web:latest
├── frontend/web:v1.0.0
├── backend/api:latest
├── backend/api:v1.0.0
├── backend/worker:latest
└── services/auth:latest
Example push commands:
docker push dcr.nexqloud.io/your-registry-name/frontend/web:latest
docker push dcr.nexqloud.io/your-registry-name/backend/api:v1.0.0
docker push dcr.nexqloud.io/your-registry-name/services/auth:latest
Naming Conventions
Recommended patterns:
# By component
frontend/component-name
backend/service-name
database/db-type
# By environment
myapp/dev
myapp/staging
myapp/production
# By version
myapp:v1.0.0
myapp:v1.1.0
myapp:latest
# Combined approach
project/component:environment-version
example: ecommerce/api:prod-v2.1.0
Repository Management Operations
Viewing Repository Details
Get detailed information about a repository:
- Click on the repository name in the console
- View:
- All tags
- Image layers
- Push history
- Size information
Copying Tags
Copy a tag to create a new reference:
# Pull existing tag
docker pull dcr.nexqloud.io/your-registry-name/myapp:v1.0.0
# Tag with new name
docker tag dcr.nexqloud.io/your-registry-name/myapp:v1.0.0 \
dcr.nexqloud.io/your-registry-name/myapp:stable
# Push new tag
docker push dcr.nexqloud.io/your-registry-name/myapp:stable
Inspecting Images
View image details locally:
# Pull image
docker pull dcr.nexqloud.io/your-registry-name/myapp:latest
# Inspect image
docker inspect dcr.nexqloud.io/your-registry-name/myapp:latest
# View image history
docker history dcr.nexqloud.io/your-registry-name/myapp:latest
Monitoring Repository Usage
Storage Usage
Monitor your registry storage consumption:
- Navigate to your registry in the console
- View storage metrics on the overview page
- See breakdown by repository
Activity Monitoring
Track repository activity:
- Recent pushes
- Pull statistics
- Active repositories
- Tag creation/deletion events
Best Practices
Tag Management
- Use semantic versioning:
v1.0.0,v1.1.0,v2.0.0 - Maintain latest tag: Always tag stable releases as
latest - Environment tags: Use
dev,staging,prodfor deployment stages - Commit tags: Include git commit SHA for traceability
Repository Organization
- Consistent naming: Establish and follow naming conventions
- Logical grouping: Group related images together
- Avoid deep nesting: Keep hierarchy shallow (max 2-3 levels)
- Documentation: Document your naming scheme for team members
Cleanup Strategy
- Regular cleanup: Remove unused tags periodically
- Keep versions: Maintain recent versions and production tags
- Retention policy: Define how long to keep old images
- Test tags: Clean up test/development tags regularly
Troubleshooting
Repository Not Visible
- Verify you pushed the image successfully
- Check you're viewing the correct registry
- Refresh the console page
- Verify your permissions
Cannot Access Repository
- Confirm authentication credentials
- Check registry permissions
- Verify network connectivity
- Ensure registry is active
Storage Quota Exceeded
- Review storage usage by repository
- Remove unused tags and images
- Consider upgrading your plan
- Optimize image sizes