Building Docker Image for Forked Source Connector with Patch

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

Exploring building a Docker image for a forked source connector with a patch and uploading it to a personal repository without using airbyte-ci. Requesting a sample Dockerfile for reference.


Question

Hello! If I wanted to fork a source connector to patch it for my own use case, how can I build a docker image with my patch to be uploaded to my own repository? Do I have to use airbyte-ci or is there another way? Is there a Dockerfile sample I can reference?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["forked-source-connector", "docker-image", "patch", "personal-repository", "dockerfile-sample"]
2

In docs https://docs.airbyte.com/connector-development/tutorials/cdk-speedrun you can find following snippet

FROM airbyte/python-connector-base:1.1.0

COPY . ./airbyte/integration_code
RUN pip install ./airbyte/integration_code

# The entrypoint and default env vars are already set in the base image
# ENV AIRBYTE_ENTRYPOINT "python /airbyte/integration_code/main.py"
# ENTRYPOINT ["python", "/airbyte/integration_code/main.py"]```
3

Most connectors use our base image already, and don’t have a dockerfile.

To make a custom image of an existing connector:

  1. Bump dockerImageTag in metadata.yaml
  2. Make your code changes
  3. airbyte-ci connectors —name=source-wat build