how to change the docker registry for connectors f...
# help-connector-development
r
how to change the docker registry for connectors from default airbyte
k
A message from kapa.ai
To change the Docker registry for connectors from the default Airbyte registry, you can use custom connectors and host your custom connector images on a private Docker registry. Here are some resources to create a private Docker registry: | Cloud provider | Service name | Documentation | | --- | --- | --- | | Google Cloud | Artifact Registry | [Quickstart](https://cloud.google.com/artifact-registry/docs/docker/quickstart) | | AWS | Amazon ECR | [Getting started with Amazon ECR](https://docs.aws.amazon.com/AmazonECR/latest/userguide/getting-started-console.html) | | Azure | Container Registry | [Quickstart](https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal) | | DockerHub | Repositories | [DockerHub Quickstart](https://docs.docker.com/docker-hub/) | | Self hosted | Open-source Docker Registry | [Deploy a registry server](https://docs.docker.com/registry/deploying/) | Once you have your custom connector image hosted on a private Docker registry, you can add it to Airbyte as a custom connector. Follow these steps: 1. Get the Docker coordinate of your custom connector from your private registry. 2. In the Airbyte UI, go to the Admin section, and click on
[+ New connector]
on the top right. 3. Provide the display name, Docker repository name (repository + image name), tag, and documentation URL for your connector. After completing these steps, your custom connector will be available in the Airbyte UI and API [source](https://docs.airbyte.com/integrations/custom-connectors). Please note that this process involves using custom connectors instead of overwriting the built-in connectors. This approach should run more smoothly and allow you to use your private Docker registry for connector images.
r
i meant while building the connector the docker image generated still has airbyte as the registry
./gradlew airbyte-integrations:connectors:source-clickhouse:build
m
You can tag the image and push to any other registry you need @Ramkumar Vaidyanathan
r
@Marcos Marx (Airbyte) yes that is what I did, just wondering if there was some kind of env variable to dictate it.
also i am hitting this error when i try to switch the docker image tag
Copy code
2023-05-26 16:29:57 WARN i.a.c.s.s.AirbyteRemoteOssCatalog(getDestinationDefinitions):44 - Unable to retrieve latest Destination list from Remote Registry. This warning is expected if this cluster does not have internet access.
java.lang.RuntimeException: Failed to fetch remote connector registry
I figure the issue,
b
@Ramkumar Vaidyanathan, any details on how you solved this?