Cannot run airbyte in dev mode

Platform, Deploy & Infra Issues
,
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: MacOS Monterey 12.6 , M1 Chip
  • Memory / Disk: 8GB / 0.5TB
  • Deployment: Docker
  • Airbyte Version: 0.40.26
  • Source name/version: None
  • Destination name/version: None
  • Step: Deployment
  • Description: Cannot run in dev mode, bootloader manifest missing. I’ve made a fresh clone of the repo, initialized my env variable according to M1 specific setup instruction but got
WARNING: The RUN_DATABASE_MIGRATION_ON_STARTUP variable is not set. Defaulting to a blank string.
WARNING: The DEPLOYMENT_MODE variable is not set. Defaulting to a blank string.
WARNING: The LOG_CONNECTOR_MESSAGES variable is not set. Defaulting to a blank string.
WARNING: The SHOULD_RUN_NOTIFY_WORKFLOW variable is not set. Defaulting to a blank string.
WARNING: The SECRET_PERSISTENCE variable is not set. Defaulting to a blank string.
WARNING: The JOB_ERROR_REPORTING_SENTRY_DSN variable is not set. Defaulting to a blank string.
WARNING: The NEW_SCHEDULER variable is not set. Defaulting to a blank string.
WARNING: The WORKER_ENVIRONMENT variable is not set. Defaulting to a blank string.
WARNING: The GITHUB_STORE_BRANCH variable is not set. Defaulting to a blank string.
WARNING: The REMOTE_CONNECTOR_CATALOG_URL variable is not set. Defaulting to a blank string.
WARNING: The TEMPORAL_HISTORY_RETENTION_IN_DAYS variable is not set. Defaulting to a blank string.
WARNING: The UPDATE_DEFINITIONS_CRON_ENABLED variable is not set. Defaulting to a blank string.
Creating network "airbyte_default" with the default driver
Creating network "airbyte_airbyte_internal" with the default driver
Creating network "airbyte_airbyte_public" with the default driver
Pulling bootloader (airbyte/bootloader:dev)...
ERROR: manifest for airbyte/bootloader:dev not found: manifest unknown: manifest unknown

Note that before that I could not build the dev version because of an issue with note yet I juste installed it with brew install node and running version 19.3.8

guillaume@Guillaumes-MBP airbyte % SUB_BUILD=PLATFORM ./gradlew build
Building Airbyte Sub Build: PLATFORM

> Configure project :
configuring docker task for airbyte-bootloader
configuring docker task for airbyte-connector-builder-server
configuring docker task for airbyte-container-orchestrator
configuring docker task for airbyte-cron
configuring docker task for airbyte-proxy
configuring docker task for airbyte-server
configuring docker task for airbyte-temporal
configuring docker task for airbyte-webapp
configuring docker task for airbyte-workers
configuring docker task for init
configuring docker task for db-lib
configuring docker task for reporter

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':airbyte-webapp:nodeSetup'.
> Failed to query the value of task ':airbyte-webapp:nodeSetup' property 'nodeArchiveFile'.
   > Could not resolve all files for configuration ':airbyte-webapp:detachedConfiguration1'.
      > Could not resolve org.nodejs:node:16.18.1.
        Required by:
            project :airbyte-webapp
         > Could not resolve org.nodejs:node:16.18.1.
            > Could not get resource 'https://nodejs.org/dist/v16.18.1/node-v16.18.1-darwin-arm64.tar.gz'.
               > Could not HEAD 'https://nodejs.org/dist/v16.18.1/node-v16.18.1-darwin-arm64.tar.gz'. Received status code 500 from server: Internal Server Error
2

I managed to get around this by brew uninstalling node and let docker install it.
However the Gradle build is still failing due to Docker factory test failing . No idea how to move forward from there.

Screenshot 2022-12-20 at 17.00.14
Screenshot 2022-12-20 at 17.00.141700×788 110 KB

3

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

4

Hello Guillaume Chevalier, it’s been a while without an update from us. Are you still having problems or did you find a solution?

5

I fixed the issue @sajarin Can’t remember how tho …