Container Registry Auth

Most jobs in Daestro run using Docker images. While you can use any public image, you might have your own private images stored in a service like Docker Hub, AWS ECR, or your own private registry.

A Container Registry Auth is a secure way to store the login details (like a username and password or an access token) for these private registries. This gives Daestro permission to pull your private images so it can use them to run your jobs.

Table of Contents

• How to Create a Container Registry Auth
• How to Update a Container Registry Auth
• How to Delete a Container Registry Auth

How to Create a Container Registry Auth

1. Go to the Container Registry Auth page in the Daestro Console.
2. Click on Add New.
3. Fill out the form with the following details:
   • Name: A simple name you’ll recognize, like My Docker Hub Account.
   • Registry URL (Optional): If you are using a registry other than the default Docker Hub (like gcr.io or a self-hosted one), enter its URL here.
   • Username: Your username for the registry.
   • Password / Personal Access Token: Your password or an access token for the registry.

Once you’ve saved the credentials, you can select this Container Registry Auth when creating a Job Definition that uses an image from that private registry.

How to Update a Container Registry Auth

For security reasons, you cannot edit the credentials of a Container Registry Auth after it has been created. If your password or token changes, you will need to delete the old entry and create a new one with the updated credentials.

How to Delete a Container Registry Auth

You can delete a set of credentials if you no longer need them. However, you can only delete a Container Registry Auth if it is not currently being used by any of your Job Definitions.