Error running airbyte-ci connectors build with dagger

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

Summary

The user is facing an error when trying to build a custom connector with dagger after switching to Airbyte version 1.0.0 locally deployed with abctl. The error message indicates a problem connecting to the docker daemon.


Question

Hi
I developed a python cdk custom connector with version 0.57.x that worked very well with locally docker compose deployed airbyte.
Now i want to switch to version 1.0.0, locally deployed with abctl
When I run airbyte-ci connectors build, dagger fails with error
`Error: Could not connect to docker daemon: Error while fetching server API version: (‘Connection aborted.’, FileNotFoundError(2, ‘No such file or directory’))``
what am i doing wrong ?


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

["python-cdk-custom-connector", "airbyte-version-1.0.0", "abctl", "dagger", "docker-daemon"]
2

Hmm, I always added --name option, e.g. airbyte-ci connectors --name=source-faker build

And then I could load image to Airbyte deployment (kind cluster) created by abctl
kind load docker-image airbyte/source-faker:dev -n airbyte-abctl

https://docs.airbyte.com/contributing-to-airbyte/developing-locally#connector-contributions

3

Just to be sure, you have Docker engine running and you get this error later during building?

4

Yes same, the whole command `airbyte-ci connectors --disable-dagger-run --show-dagger-logs --name=source-sftp-bulk build``

5

And yes docker is running.

6

Just wondering if it’s because airbyte is running into kind

7

So I don’t understand why building a new connector needs to access to airbyte, it doesn’t right ?

8

I don’t think so. I stopped airbyte-abctl-control-plane and it’s not trying to connect to airbyte.
On my macOS, building connector works fine and image is loaded only to Docker engine (not Airbyte deployment by abctl)

9

ok so it should work, thanks

10

which versions do you have?

airbyte-ci, version 4.35.6
$ airbyte-ci --ci-requirements
{"dagger_version": "0.9.6", "dagger_engine_image": "<http://registry.dagger.io/engine:v0.9.6|registry.dagger.io/engine:v0.9.6>"}```
11 
[16:36:00] INFO     root: Setting working directory to /Users/guifesquet/TBOX/SOFTS/airbyte                                                             ensure_repo_root.py:58
airbyte-ci, version 4.35.6
➜  airbyte-ci git:(heads/v1.0.0) airbyte-ci --ci-requirements                                                                                                   &lt;aws:default&gt;
[16:36:20] INFO     root: Setting working directory to /Users/guifesquet/TBOX/SOFTS/airbyte                                                             ensure_repo_root.py:58
{"dagger_version": "0.9.6", "dagger_engine_image": "<http://registry.dagger.io/engine:v0.9.6|registry.dagger.io/engine:v0.9.6>"}```
12

I’ll check my docker installation, and I’ll get back to you

13

It looks like something with dagger and Docker socket. I think I’ve seen during first run pulling dind image (docker-in-docker)

14

I had this issue. I solved it by enabling Allow the default Docker socket to be used option in Docker -> Settings -> Advanced.

15

Yeah, I guess I recommended this option somebody few months ago

16

It works, thanks both of you