Overview
The Generic Container Registry option allows you to connect any Docker-compatible or OCI-compliant container registry to Qovery. This provides flexibility to use your preferred registry solution or self-hosted registries.If your registry supports the standard
docker login format, you can connect it using the Generic registry option.Supported Registries
The Generic option works with:- Harbor - Open-source cloud-native registry
- Nexus Repository - Universal artifact repository
- JFrog Artifactory - Universal DevOps platform
- Quay.io - Red Hat’s container registry
- Self-hosted Docker Registry - Docker’s official registry
- Any OCI-compliant registry - Following OCI Distribution Spec
Configuration in Qovery
1
Gather Registry Information
Collect the following from your registry:
- Registry URL (must include
https://) - Username or access key
- Password or access token
- Authentication method (Basic Auth)
2
Access Organization Settings
Navigate to Organization Settings → Container Registries in Qovery
3
Add Registry
Click Add Registry
4
Select Generic Registry
Choose Generic Container Registry from the registry type dropdown
5
Enter Registry Details
Provide:
- Name: Descriptive name for the registry
- Registry URL: Full URL with protocol (e.g.,
https://registry.example.com) - Username: Authentication username
- Password: Authentication password or token
6
Optional: TLS Configuration
If using self-signed certificates:
- Enable Skip TLS Verification (not recommended for production)
7
Save
Qovery will test the connection and save the configuration
Registry-Specific Examples
Harbor
Nexus Repository
JFrog Artifactory
Quay.io
Self-Hosted Docker Registry
Image Format
The image format depends on your registry configuration: Standard format:registry.example.com/production/api:v1.0.0harbor.company.com/project/frontend:latestnexus.internal.net/docker/backend:stable
Authentication Methods
Most registries support:- Basic Authentication (username + password)
- Token-based Authentication (username + token)
- Robot Accounts (service accounts with limited permissions)
Troubleshooting
Connection Failed
Connection Failed
Check:
- Registry URL is correct and includes
https:// - Registry is accessible from Qovery (not behind firewall)
- Credentials are valid
- Username format is correct (some registries use email)
TLS Certificate Errors
TLS Certificate Errors
Solutions:
- Ensure TLS certificates are properly configured
- Use certificates from trusted CA
- For development only: Enable “Skip TLS Verification”
Authentication Errors
Authentication Errors
Verify:
- Username is correct (not email if registry expects username)
- Password/token hasn’t expired
- Account has necessary permissions
- Using token instead of password if required
Best Practices
Use Service Accounts
Create dedicated service accounts for Qovery instead of using personal credentials
Rotate Credentials
Regularly rotate registry access tokens and passwords
Proper TLS
Always use valid TLS certificates in production environments
Least Privilege
Grant minimum required permissions (read-only for deployments)