gcloudcredential helper to log in to your Artifact registry. Please run the command detailed here to authenticate your local environment/CI environment to your Artifact registry. Run the same authentication flow on your Compute Engine instance. If you do not want to use
gcloud, GCP offers other authentication methods detailed here.
aws ecr get-login-password --region region | docker login --username AWS --password-stdin aws_account_id.dkr.ecr.region.amazonaws.comYou can find details about this command and other available authentication methods here. You will have to authenticate your local/CI environment (where you build your image) and your EC2 instance where your Airbyte instance is running.
az acr login --name <registry-name>You can find details about this command here You will have to authenticate both your local/CI environment/ environment (where your image is built) and your Azure Virtual Machine instance where the Airbyte instance is running.
JOB_KUBE_MAIN_CONTAINER_IMAGE_PULL_SECRETenvironment variable on the
airbyte-workerpod. The value must be the name of your previously created Kubernetes Secret.
docker build . -t my-custom-connectors/source-custom:0.1.0
docker tagcommand. The structure of the remote tag depends on your cloud provider's container registry service. Please check their online documentation linked at the top.
docker push <image-name>:<tag>to push the image to your private Docker registry.
docker pull <image-name>:<tag>if you are using our
docker-composedeployment, or start a pod that is using the connector image.