airbytehq / airbytehq/airbyte

Is it possible to use a local connector registry instead of a remote one ?

Open
#71,050 4 comments 3 reactions 0 assignees View on GitHub
area/platform autoteam community needs-triage team/compose team/platform-move type/bug
Dominant language
Python
Stars
22.1k
Forks
5.3k
PR merge metrics
PR metrics pending

Description

### Helm Chart Version

2.0.19

### What step the error happened?

On deploy

### Relevant information

airbyte-bootloader pods failing in bootstrap phase during connection to the remote connector registry
the value of the following env var is set as follows:
CONNECTOR_REGISTRY_SEED_PROVIDER: remote
This is the default by the chart.
We are running on an air-gapped environment.
Is there a way to circumvent this phase ?
Are we able to supply the json file that is being retrieved by other means ?

### Relevant log output

```shell
2025-12-30 10:15:39,757 [main] INFO i.a.b.DefaultPostLoadExecutor(execute):30 - Updating connector definitions
2025-12-30 10:15:40,215 [main] ERROR i.a.b.ApplicationKt(main):28 - Unable to bootstrap Airbyte environment.
java.lang.RuntimeException: Failed to fetch remote connector registry
at io.airbyte.config.specs.RemoteDefinitionsProvider.getRemoteConnectorRegistry(RemoteDefinitionsProvider.kt:214)
at io.airbyte.config.specs.$RemoteDefinitionsProvider$Definition$Intercepted.$$access$$getRemoteConnectorRegistry(Unknown Source)
at io.airbyte.config.specs.$RemoteDefinitionsProvider$Definition$Exec.dispatch(Unknown Source)
at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invoke(AbstractExecutableMethodsDefinition.java:456)

Thank you!
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.