Public vs Private Images
Public images from any registry, including Docker Hub, work with Pipecat Cloud without additional configuration. However, we strongly recommend using private images for better data privacy and security when deploying production agents. For Docker Hub specifically, even when using public images, we recommend setting up image pull secrets due to Docker Hub’s low rate limits for unauthenticated pulls. See our Image pull secrets guide for setup instructions.Private Registry Setup
For private images from any registry (including private Docker Hub repositories), you’ll need to configure image pull secrets for authentication.Docker Hub Private Images
For private Docker Hub repositories, see the Image pull secrets section in our Secrets guide for complete setup instructions.Other Private Registries
For other private registry providers, choose your platform below for detailed setup instructions:Google Cloud Artifact Registry
Complete setup guide for GCP Artifact Registry, including service account
configuration and authentication.
Amazon ECR
Detailed AWS ECR integration with automatic token refresh setup for
continuous deployment.
General Process
All private registry integrations follow a similar pattern:- Authenticate Docker with your registry locally
- Create image credentials in Pipecat Cloud using the CLI
- Reference credentials in your deployment configuration
- Deploy your agent using the private image
pcc-deploy.toml
file: