Skip to content

Update private Docker registry docs: remove GCR #257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Hkhan161 merged 1 commit into from
Dec 16, 2025
+1 −7
Merged

Update private Docker registry docs: remove GCR #257

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions cerebrium/container-images/private-docker-registry.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: "Using Private Docker Registries"
description: "How to authenticate, pull, and use private Docker images as base images in your deployments."
---

Cerebrium supports using your own private Docker images as base images for your deployments - including images from Docker Hub, AWS ECR, Google Container Registry, or any Docker-compatible private registry.
Cerebrium supports using your own private Docker images as base images for your deployments - including images from Docker Hub and AWS ECR.

Our build system securely pulls your private image using the Docker credentials stored in your ~/.docker/config.json, and then builds your app on top of that image. Since these credentials are used during deployment, they should be team-accessible rather than tied to a single individual.

Expand Down Expand Up @@ -33,12 +33,6 @@ aws ecr get-login-password --region us-east-1 | \
123456789.dkr.ecr.us-east-1.amazonaws.com
```

**Google Container Registry:**

```bash
gcloud auth configure-docker
```

**Generic Registry:**

```bash
Expand Down