Overview
Dokploy supports connecting to Docker container registries to pull base images and push built application images. Configure multiple registries for different purposes.Registry Types
Dokploy supports two types of container registries:enum
default:"cloud"
Registry type
cloud- Cloud-hosted registry (Docker Hub, GitHub Container Registry, etc.)selfHosted- Self-hosted registry
Configuration
Basic Settings
string
required
Display name for the registry
string
required
Registry URL
string
required
Registry username or access key
string
required
Registry password, access token, or secret
string
Prefix for image names (useful for namespacing)
Popular Registries
Docker Hub
The default public container registry.Creating Docker Hub Token
- Log in to Docker Hub
- Go to Account Settings > Security
- Click “New Access Token”
- Give it a description and set permissions
- Copy the token (shown only once)
GitHub Container Registry (GHCR)
Store container images alongside your GitHub repositories.Creating GitHub Token
- Go to GitHub Settings > Developer settings > Personal access tokens
- Generate new token (classic)
- Select scopes:
write:packages- Upload packagesread:packages- Download packagesdelete:packages- Delete packages (optional)
- Copy the token
AWS Elastic Container Registry (ECR)
Amazon’s container registry service.AWS ECR tokens expire after 12 hours. Consider using an IAM role or automated token refresh.
Google Container Registry (GCR)
Google Cloud’s container registry.Azure Container Registry (ACR)
Microsoft Azure’s container registry.Self-Hosted Registry
Connect to your own Docker registry.Testing Registry Connection
Before using a registry, test the connection:Test Before Creating
Test Existing Registry
Managing Registries
List All Registries
Passwords are not returned in list responses for security.
Get Single Registry
Update Registry
Delete Registry
Using Registries
For Pulling Images
When deploying applications, Dokploy can pull base images from configured registries:For Pushing Built Images
After building an application, Dokploy can push the image to a registry:Rollback Registry
Store previous image versions for rollbacks:Server-Specific Registries
For multi-server deployments, specify which server to test against:Authentication Methods
Username/Password
Basic authentication with username and password:Access Tokens
Many registries use personal access tokens:Service Accounts
Cloud providers often use JSON key files:Security Best Practices
Credential Management
- Rotate Regularly: Change registry passwords every 90 days
- Least Privilege: Grant only necessary permissions
- Separate Credentials: Use different credentials for dev/prod
- Token Expiration: Use short-lived tokens when possible
Registry Security
- Private Registries: Use private registries for proprietary images
- Image Scanning: Enable vulnerability scanning
- Image Signing: Sign images for authenticity
- Access Logs: Monitor registry access logs
Network Security
- HTTPS Only: Always use HTTPS for registry URLs
- VPC/Private Network: Use private networks when possible
- Firewall Rules: Restrict registry access by IP
- Rate Limiting: Implement rate limits to prevent abuse
Troubleshooting
Connection Issues
Login Failed
Login Failed
- Verify username and password are correct
- Check if credentials have expired
- Ensure registry URL is correct
- Confirm registry is accessible from server
Image Push Failed
Image Push Failed
- Verify write permissions
- Check disk space on server
- Ensure image name matches registry prefix
- Confirm network connectivity
Image Pull Failed
Image Pull Failed
- Verify read permissions
- Check if image exists in registry
- Ensure correct image name and tag
- Confirm credentials are valid
Common Errors
Database Schema
Registry configuration is stored in theregistry table: