█ [10.85s] ERROR airbyte-ci connectors --name=source-local build ┃ [134603] INFO root: Setting working directory to /Users/guifesquet/TBOX/SOFTS/airbyte ensure_repo_root.py: ┃ 58 ┃ [134605] INFO root: Setting working directory to /Users/guifesquet/TBOX/SOFTS/airbyte ensure_repo_root.py: ┃ 58 ┃ INFO pipelines: airbyte-ci is up to date. Installed version: 4.35.6. Latest version: 4.35.6 auto_update.py: ┃ 88 ┃ INFO pipelines: Called with dagger run: True airbyte_ci.py:1 ┃ 26 ┃ Usage: airbyte-ci [OPTIONS] COMMAND [ARGS]... ┃ Try ‘airbyte-ci --help’ for help. ┃ ┃ Error: Could not connect to docker daemon: Error while fetching server API version: (‘Connection aborted.’, FileNotFoundError(2, ‘No such file or directory’)) ┻ • Engine: 0ab40a5b64ea (version v0.9.6)

Based on the error message you provided, it seems like the

airbyte-ci

command is unable to connect to the Docker daemon. This could be due to several reasons such as Docker not running, Docker not installed, or issues with Docker's configuration. Unfortunately, the knowledge sources provided do not contain specific solutions to this issue. However, you can try the following general troubleshooting steps: 1. Ensure Docker is installed and running on your machine. You can verify this by running

docker version

or

docker info

in your terminal. 2. Check if Docker is properly configured and the Docker daemon is accessible. The configuration might vary depending on your operating system. 3. If you're running the command in a Docker container, ensure the Docker daemon is accessible from within the container. This usually involves mounting the Docker socket into the container. If the issue persists, I recommend checking Docker's official documentation or reaching out to the Airbyte community for further assistance.

@kapa.ai docker is running when I run

airbyte-ci connectors --name= build

it says Error: Could not connect to docker daemon: Error while fetching server API version: (‘Connection aborted.’, FileNotFoundError(2, ‘No such file or directory’))

The error message you're seeing typically indicates that the Docker daemon is not running or not accessible. Here are a few things you can try: 1. Ensure Docker is running: You can verify this by running a simple Docker command like

docker ps

. If Docker is running, you should see a list of running containers. If not, you'll need to start Docker. 2. Check Docker daemon access: Depending on your system configuration, you might need to use

sudo

to run Docker commands. Try running the command with

sudo

. 3. Check Docker version: Make sure you're running a compatible version of Docker. You can check your Docker version by running

docker version

. If you're still having trouble, it might be helpful to review the [Airbyte documentation](https://docs.airbyte.com/connector-development/tutorials/the-hard-way/build-a-connector-the-hard-way#1-publish-the-docker-image) or the [Docker documentation](https://docs.docker.com/get-docker/). Please note that the command you're trying to run seems to be missing the connector name. The correct format should be

airbyte-ci connectors --name source-stock-ticker-api build

where

source-stock-ticker-api

should be replaced with the name of your connector.

ok @kapa.ai but if it’s not docker what about Error while fetching server API version: (‘Connection aborted.’, FileNotFoundError(2, ‘No such file or directory’))

A message from kapa.ai

The error message

Error while fetching server API version: (‘Connection aborted.’, FileNotFoundError(2, ‘No such file or directory’))

typically indicates that the Docker client is unable to communicate with the Docker daemon. This could be due to several reasons: 1. Docker daemon is not running: As mentioned earlier, you can verify this by running a simple Docker command like

docker ps

. 2. Incorrect Docker daemon socket: Docker client communicates with the Docker daemon through a socket file, typically located at

/var/run/docker.sock

. If this file is missing or inaccessible, you might see this error. You can check if this file exists and is accessible. 3. Network issues: If you're running Docker in a networked environment (like a Docker Swarm), network issues might prevent the Docker client from reaching the Docker daemon. 4. Docker version mismatch: If your Docker client and Docker daemon versions are significantly different, they might not be able to communicate correctly. You can check your Docker version by running

docker version

. If none of these solutions work, you might want to check the [Airbyte Github issues](https://github.com/airbytehq/airbyte/issues/38570) for similar problems or the [Docker documentation](https://docs.docker.com/engine/reference/commandline/dockerd/) for more information on how the Docker daemon works.