This topic provides settings and permissions for the Docker connector. You can use this connector to connect to DockerHub, Harbor, Quay, and other Docker V2 compliant container registries, such as GitHub Container Registry.
- Docker registry rate limits: Harness is restricted by the limits of the Docker repo, such as Docker Hub limits for pulling Docker images from Docker repos.
- Docker Registries in Cloud Platforms: The Docker connector is platform-agnostic and can be used to connect to any Docker container registry. Harness also provides first class support for registries in AWS and GAR through AWS connectors and Google Cloud Platform (GCP) connectors.
Create a Docker connector
- In Harness, go to the module and project where you want to create the connector, and select Connectors (under Project Setup). You can also create connectors at the account level.
- Select New Connector, and then select Docker Registry.
- Configure the Docker connector settings as described in the sections below.
- Select Save and Continue, wait for the connectivity test to run, and then select Finish.
- In the list of connectors, make a note of your Docker connector's ID. Use the ID in your pipeline YAML, such as
Connector metadata settings
- Name: Enter a name for this connector. Harness creates an Id (Entity Identifier) based on the name.
- Description: Optional text string.
- Tags: Optional. Go to the Tags reference.
Select the Docker registry platform: DockerHub, Harbor, Quay or Other.
If you select Other, the registry must be Docker V2 compliant.
Docker Registry URL
The URL of the Docker registry. This is usually the URL used for your docker login credentials.
To connect to a public Docker registry like Docker Hub, use
To connect to a private Docker registry, use
You can authenticate anonymously or by username and password.
- Username and password
- Username: Enter the username for your Docker registry account.
- Password: In your Docker registry, create a personal access token with Read, Write, Delete permissions. Then, create a Harness secret for your Docker registry personal access token.
Make sure the connected user account has read permission for all repositories as well as access and permissions to pull images and list images and tags.
For more information, go to the Docker documentation on Docker Permissions.
If you use anonymous access for a Kubernetes deployment, make sure
imagePullSecrets is removed from the container specification. This is standard Kubernetes behavior and not related to Harness specifically.
Select connectivity mode
You can connect through a Harness Delegate or the Harness Platform. If you plan to use this connector with Harness Cloud build infrastructure, you must select Connect through Harness Platform.