Private Registry

Learn how to connect a private Docker registry to Trickest to use private images in your tools.

Exclusive access to private Docker registry integration is provided solely for Enterprise users. If you are interested in learning more about the Enterprise Edition, please contact us.

About Private Registry

The Private Docker Registry integration works with the Private Tools feature and lets you use private Docker images in Trickest workflows. By connecting a secure private registry to Trickest, you can include proprietary tools in your Trickest workflows without exposing them publicly.

Prerequisites

Before proceeding, make sure you have:

• A Trickest account with Private Registry access.
• Access to the private Docker registry you want to connect.

Obtaining Credentials for Your Private Registry

Trickest supports Docker Hub, GitHub Packages, and any registry that supports the Docker Registry HTTP API, including AWS ECR.

To connect a registry, you will need a username and password or access token. The exact steps depend on your registry provider. Use the links below to generate the required credentials:

• AWS ECR
• Docker Hub
• GitHub Packages

Connect Your Private Registry to Trickest

1. Go to the Docker Registry settings page.

2. Choose your registry provider from the list.

   • If your provider isn’t listed (for example, AWS ECR), select Basic.

3. Click Connect Provider.

4. Fill in the connection details:

   • Name – A label you’ll recognize.
   • URL – Include the namespace (e.g. aws_account_id.dkr.ecr.region.amazonaws.com/namespace). This field is required only for the Basic registry type.
   • Username and password – Use the credentials you obtained.

5. Click Connect.

After connecting, you can use images from your private registry in your private tool configurations without any extra steps.