Platform
Private registries
Deploy private images from GHCR, GitLab, Docker Hub and other registries with read-only registry credentials.
Public images need nothing extra. To deploy a private image, add registry credentials to its project: a username and a read-only token for one registry host. When an image from that host can't be pulled anonymously, it is checked and pulled with them — automatically, no per-service setting.
How it works #
- One set per registry and project (up to 20 per project). Every member of the team sees them (host, username, last use); only the team owner can add, rotate and delete them — or an API key, which only the owner can create.
- Only when needed. Every image is first checked anonymously. Credentials are used — and the service pulls with them — only when the registry asks for authentication. Public images keep working even if a token expires.
- Checked before deploy. When you create a service or deploy a new image, we resolve it with the credentials: a refused token shows Registry rejected the credentials for ghcr.io right away, and an image the token can't see shows Image not found or no access. Nothing is deployed in either case.
- Write-only. The token is stored encrypted. The dashboard, the API and the MCP server show the host, the username and when it was last used — never the token.
- Sent only to that registry. We send the credentials to the registry's own host and its own login service — never along a redirect or to a download CDN.
- Rotate them any time: services keep using them, and new pulls use the new token. Deleting them leaves running containers alone, but a service whose image needs them can't be deployed again until you add credentials for that registry and Redeploy.
Add them in the dashboard under Projects → your project → Registry credentials. Use a token that can only read packages: if it leaks, nobody can push to your registry with it.
GitHub Container Registry (ghcr.io) #
- In GitHub, open Settings → Developer settings → Personal access tokens → Tokens (classic) and generate a token with only the
read:packagesscope. (Fine-grained tokens can't read packages yet.) - Add credentials with host
ghcr.io, your GitHub username, and the token. - For an organization's package, the token's owner needs read access to the package.
GitLab (registry.gitlab.com) #
- In the project (or group), open Settings → Repository → Deploy tokens and create a token with only the
read_registryscope. - Add credentials with host
registry.gitlab.com, the deploy token's username (likegitlab+deploy-token-123) and the token.
Docker Hub #
- In Docker Hub, open Account settings → Personal access tokens and create a token with Read-only access.
- Add credentials with host
docker.io, your Docker Hub username and the token.
Like for every registry, the credentials are used only for images that need them; public Docker Hub images are pulled anonymously.
Other well-known registries #
The same works for these registries too. Use the host as it appears in the image reference and a read-only token:
docker.io— Docker Hubghcr.io— GitHub (ghcr.io)quay.io— Quay.ioregistry.gitlab.com— GitLabpublic.ecr.aws— Amazon ECR Publicmcr.microsoft.com— Microsoft (mcr.microsoft.com)gcr.io— Google (gcr.io)- Regional Google hosts such as
europe-docker.pkg.devandeu.gcr.io(use a service account JSON key with read access: username_json_key, the whole key file as the password — line breaks are fine).
Self-hosted registries (Harbor, Nexus, your own domain) #
Self-hosted registries (Harbor, Nexus, GitLab self-managed, a registry on your own domain) aren't available yet — we're finishing the network safeguards for pulling from them. Until then, push the image to one of the registries above. Tell us which registry you use, so we can let you know when it's ready.
Amazon ECR private registries use short-lived login tokens and aren't supported yet. Tell us if you need them.
API and MCP #
With an API key that has the services:manage scope (listing needs services:read). API keys are created by the team owner, so they may manage credentials:
curl -X POST https://api.quicktane.com/v1/projects/42/registry-credentials \
-H "Authorization: Bearer $QUICKTANE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"host": "ghcr.io", "username": "octocat", "password": "'"$GHCR_READ_TOKEN"'"}'
Rotate with PUT /v1/projects/{id}/registry-credentials/{credentialId} (username, password) and delete with DELETE on the same path. From AI tools, the MCP server offers set_registry_credential, list_registry_credentials and delete_registry_credential.
Something missing or wrong? Tell us — or open a ticket from the dashboard.