-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker build fails for python source connectors in development #6443
Comments
thanks @marc-marketparts ! we're going to investigate the best way to solve this problem. Thanks for give some directions using a fixed version of CDK. @bazarnov fyi! |
@marc-marketparts According to logs you are using python:3.7.11-alpine3.14 base image to build your connector. Unlike python:3.7-slim this is a very minimalist and has no gcc package required to build multidict and yarl packages which go with 0.23 cdk version. As a solution you can either switch to python:3.7-slim image or if you would like to go with python:3.7.11-alpine3.14 you can add gcc package to your dockerfile:
|
@antixar could this be an issue in our usage of alpine images? |
Hi All, |
Adding build-base to the Dockerfile works well. IMHO, to handle security and airbyte cdk updates more transparently, the Dockerfile generated by the python generator should reference an Airbyte docker image (as the java source seems to do) instead of the Alpine/Python image. |
Agree. I proposed same. |
Enviroment
Current Behavior
Building a local docker image of a new python source connector fails.
(docker build . -t airbyte/source-test:dev)
Expected Behavior
Docker build should succeed.
Logs
LOG
Steps to Reproduce
To be noticed:
A possible workaround to this issue is downgrading manually the airbyte cdk version in setup.py
The build succeeds with airbyte-cdk==0.1.22
Are you willing to submit a PR?
no
The text was updated successfully, but these errors were encountered: