https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> I'm trying to install airbyte-ci us...
# replication-ask-ai
d
@kapa.ai I'm trying to install airbyte-ci using this command, 
make tools.airbyte-ci-dev.install
and getting following error,
Copy code
python3.10 not found on the path.
Please install Python 3.11 using pyenv:
1. Install pyenv if not already installed:
   brew install pyenv
2. Install Python 3.10 using pyenv:
   pyenv install 3.10.12
make: *** [tools.airbyte-ci-dev.install] Error 1
k
The knowledge sources don’t describe this exact error flow, but they do clarify the expected Python version and how 
airbyte-ci
is typically installed. From the docs, current local development prerequisites require Python 3.10 (managed via 
pyenv
is recommended). [Developing locally 2.0] Your error message is slightly inconsistent (it first says 
python3.10 not found
but then tells you to “install Python 3.11” and then “Install Python 3.10 using pyenv”), which suggests the script is just checking for a specific Python version on 
PATH
and not finding it. Based on the available information, the way forward is: 1. Install pyenv (if you haven’t yet):
Copy code
brew install pyenv
2. Install Python 3.10.x with pyenv (the docs use 3.10; your message suggests 3.10.12):
Copy code
pyenv install 3.10.12
   pyenv global 3.10.12
3. Ensure 
python3.10
is on your PATH Open a new shell and verify:
Copy code
python3.10 --version
If that works and shows 3.10.x, re-run:
Copy code
make tools.airbyte-ci-dev.install
If after doing this you still see the same error, the knowledge sources don’t provide further documented troubleshooting steps for this specific case. In that situation, the forum suggests an alternative: installing 
airbyte-ci
directly via 
pip
from the 
pipelines
directory or from PyPI, instead of using the 
make
target. [Trouble installing airbyte-ci] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
d
@kapa.ai
Copy code
dilan.silva@LKROMDISILVA01 airbyte % pyenv install 3.10.12
pyenv: /Users/dilan.silva/.pyenv/versions/3.10.12 already exists
continue with installation? (y/N) n
dilan.silva@LKROMDISILVA01 airbyte % pyenv global 3.10.12
dilan.silva@LKROMDISILVA01 airbyte % python3.10 --version
Python 3.10.12
dilan.silva@LKROMDISILVA01 airbyte % make tools.airbyte-ci-dev.install
python3.10 not found on the path.
Please install Python 3.11 using pyenv:
1. Install pyenv if not already installed:
   brew install pyenv
2. Install Python 3.10 using pyenv:
   pyenv install 3.10.12
make: *** [tools.airbyte-ci-dev.install] Error 1
getting the same error,
k
The knowledge sources don’t describe this exact 
python3.10 not found on the path
behavior for 
make tools.airbyte-ci-dev.install
, so I can’t say precisely why the Makefile is failing. I can only rely on what is documented about 
airbyte-ci
and its installation. From the docs and issues: • Airbyte development expects Python 3.10 managed via 
pyenv
. [Developing locally 2.0] • There are known rough edges with the 
make tools.airbyte-ci.*
targets and environment/OS specifics; some users work around this by installing 
airbyte-ci
via 
pip
instead of the Make target. [airbyte-ci issue; Trouble installing airbyte-ci] Given that: 1. You’ve confirmed:
Copy code
pyenv global 3.10.12
   python3.10 --version  # -> Python 3.10.12
so 
python3.10
is available in your interactive shell. 2. The Make target still says “python3.10 not found on the path”, which suggests the script that 
make
runs is not seeing the same PATH / pyenv shims as your interactive shell (e.g., different shell, non‑login shell, or missing pyenv init in the environment where 
make
runs). The knowledge sources don’t provide a documented fix for that mismatch. What is documented as an alternative is: • Install 
airbyte-ci
directly with 
pip
instead of using 
make
: > “The easiest way to install it is probably to just cd into pipelines directory and 
pip install .
> Or install from pypi.” [Trouble installing airbyte-ci] Concretely, based on that:
Copy code
# Ensure you are using Python 3.10.12 via pyenv
pyenv global 3.10.12
python --version  # should show 3.10.12

# Option A: install from the pipelines directory (if you have the repo)
cd airbyte-ci/connectors/pipelines  # adjust to actual pipelines dir in your checkout
pip install .

# Option B: install from PyPI (if published for your version)
pip install airbyte-ci
If you specifically need the 
-dev
variant that 
tools.airbyte-ci-dev.install
would give you, the knowledge sources don’t document a manual equivalent command, so I can’t reliably reconstruct it. Given the limitations of the available docs, if 
pip install
works for you, that’s the path the community has used when 
make tools.airbyte-ci.*
fails on macOS. [Trouble installing airbyte-ci] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
d
@kapa.ai Tried pip but still no success,
Copy code
pip install airbyte-ci   
ERROR: Could not find a version that satisfies the requirement airbyte-ci (from versions: none)
ERROR: No matching distribution found for airbyte-ci
k
The knowledge sources don’t document a clean, universal way to fix this specific combination of issues on macOS (Makefile not seeing 
python3.10
, and 
airbyte-ci
not being available on PyPI), so I’m limited to what they explicitly show. From the docs: • Local development requires Python 3.10 (managed via 
pyenv
is recommended). [Developing locally 2.0] • 
airbyte-ci
is deprecated and being phased out; most commands now have equivalents in 
poe
. [airbyte-ci deprecated] • On Mac Silicon, maintainers explicitly suggest installing from source (the “pipelines” directory) or using a Linux environment when 
make tools.airbyte-ci.*
is troublesome. [Trouble installing airbyte-ci] Relevant bits from that Mac Silicon thread: > “The easiest way to install it is probably to just cd into pipelines directory and 
pip install .
> Or install from pypi.” [Trouble installing airbyte-ci] Given that: 1. 
pip install airbyte-ci
fails That’s consistent with the forum comment: PyPI may not have a package matching your environment or version; the docs don’t guarantee that 
airbyte-ci
is always installable from PyPI. 2. Makefile still says 
python3.10 not found
even though your shell sees it The docs don’t show how that Make target is implemented, so I can’t reliably tell you how to patch it. It’s likely an environment/`pyenv` init issue, but that’s not described in the sources. 3. Documented workaround: install from source instead of 
make
or PyPI If you have the Airbyte repo checked out, the maintainers’ suggested approach is:
Copy code
# From the Airbyte repo root
   cd airbyte-ci/connectors/pipelines   # or the actual pipelines dir in your checkout
   pyenv global 3.10.12                 # ensure Python 3.10 is active
   python --version                     # should show 3.10.12
   pip install .
This is the only concrete, documented workaround for Mac in the knowledge sources. [Trouble installing airbyte-ci] 4. If that still doesn’t work The same thread notes that one user ultimately ran 
airbyte-ci
successfully on a Linux EC2 instance instead of macOS, due to Docker / 
dockerd
and tooling friction on Mac Silicon. [Trouble installing airbyte-ci] Because 
airbyte-ci
is deprecated and the docs now recommend using 
poe
for most tasks, you may also want to check whether you can achieve what you need without 
airbyte-ci
at all, using the newer connector development tooling. [airbyte-ci deprecated] If you can share what you’re trying to do with 
airbyte-ci
(e.g., build a specific connector, run tests), I can check whether there’s a documented 
poe
or other replacement command in the provided sources. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
d
@kapa.ai If airbyte ci is deprecated then what is the command to build and deploy the code to cocker ?
k
The knowledge sources say that 
airbyte-ci
is deprecated and that most of its commands now have simpler equivalents in Poe the Poet, but they do not list a single universal replacement command for “build and deploy to Docker.” [airbyte-ci deprecated] What is documented: 1. Use Poe instead of 
airbyte-ci
for connector tasks You should install Poe and then run it from the Airbyte repo or from a connector directory. [Tooling]
Copy code
# from the Airbyte repo root
   poe
or, inside a specific connector directory:
Copy code
cd airbyte-integrations/connectors/source-<your-source>
   poe
This will list the available tasks (e.g., 
build
, 
check-all
, etc.) for that connector. The exact task names can vary by connector type (Python, Java, manifest-only), so the docs explicitly say to run 
poe
to discover them. [Tooling] 2. How to use a locally built connector image in Airbyte Once you have built a Docker image for your connector (for example, `airbyte/source-`source-name`:dev`), the documented steps to “deploy” it into a local 
abctl
Airbyte instance are: [Developing locally 2.0]
Copy code
# load the local image into the kind cluster used by abctl
   kind load docker-image airbyte/source-<source-name>:dev -n airbyte-abctl
Then in the UI: ◦ Go to 
http://localhost:8000/
◦ Log in ◦ Workspace settings → Sources or Destinations ◦ Edit your connector ◦ Set the version to your Docker tag (default example: 
dev
) ◦ Click Change After that, syncs using that connector will run with your local Docker image. [Developing locally 2.0] Because the knowledge sources don’t show the exact Poe command that replaces 
airbyte-ci connectors --name ... build
, I can’t safely invent it. The documented approach is: • Use Poe in the connector directory to discover and run the appropriate build task. • Then use 
kind load docker-image ...
and update the connector version in the UI to use your built image. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
d
@kapa.ai When I use 
poe
command in my connector directory I can see the following commands list, I cannot find a command to build the connector,
Copy code
Configured tasks:
  get-connector-name          
  fetch-secrets               
  install                     
  install-cdk-cli             
  install-unit-tests-project  
  test-all                    
  test-unit-tests             
  test-integration-tests      
  format-check                
  lint-check                  
  lock                        
  get-language                
  get-base-image              
  get-version
  run-cat-tests
k
The knowledge sources don’t document a 
poe
task named 
build
for connectors, and your task list confirms there isn’t one in your connector’s config. So there is no documented Poe-based build command I can point you to for your case. What is documented are two supported ways to get a Docker image for a connector: ------------------------- 1. Use 
airbyte-ci
(preferred in the docs) All the “build connector image” instructions still reference 
airbyte-ci
as the way to build the image:
Copy code
airbyte-ci connectors --name source-<source-name> build
# produces: airbyte/source-<source-name>:dev
[Acceptance tests ref] This is also what the “Developing locally / Connector contributions” section uses before loading the image into `kind`/`abctl`. [Developing locally – connector contributions] Given your earlier install issues, I realize this is exactly what you’re trying to avoid, but it is the only documented build path for Python/low‑code connectors besides writing your own Dockerfile. ------------------------- 2. Build with your own 
Dockerfile
(alternative, not preferred) The docs describe a manual Docker build path if you don’t want to rely on `airbyte-ci`: 1. Create a 
Dockerfile
in the connector root, e.g.:
Copy code
FROM airbyte/python-connector-base:1.1.0

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

   # Entrypoint is already set in the base image, but for clarity:
   ENV AIRBYTE_ENTRYPOINT "python /airbyte/integration_code/main.py"
   ENTRYPOINT ["python", "/airbyte/integration_code/main.py"]
2. Build the image:
Copy code
docker build . -t airbyte/source-<your-source-name>:dev
[Acceptance tests ref] This method is explicitly “not preferred, and is not supported for certified connectors,” but it is documented and does not require 
airbyte-ci
. [Acceptance tests ref] ------------------------- 3. “Deploy” the built image to your local Airbyte Once you have an image (from either method above):
Copy code
kind load docker-image airbyte/source-<your-source-name>:dev -n airbyte-abctl
Then in the UI: • Go to 
http://localhost:8000/
• Workspace settings → *Sources*/*Destinations* • Edit your connector • Set the version to 
dev
(or your chosen tag) • Click Change Now syncs will use your local image. [Developing locally – connector contributions] ------------------------- Because the knowledge sources don’t show any Poe task that builds a Docker image, and your 
poe
task list doesn’t include one, the only documented options are: • Fix 
airbyte-ci
and use 
airbyte-ci connectors --name ... build
, or • Use the manual 
Dockerfile
+ 
docker build
approach. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
2 Views
Open in Slack
PreviousNext
Powered by