yuan sun
05/19/2023, 1:52 AMkapa.ai
05/19/2023, 1:52 AMkapa.ai
05/19/2023, 1:54 AMdocker pull
the connector's image, which can be hundreds of megabytes in size. Under poor connectivity conditions, the request to pull the image may take a very long time or time out. This issue is more likely to occur if your internet speed is less than 30 Mbps down or if you're running bandwidth-consuming workloads concurrently with Airbyte. You can run a [speed test](https://fast.com/) to verify your internet speed [^1^]. One workaround is to manually pull the latest version of every connector you'll use and then reset Airbyte. Note that this will remove any configured connections, sources, or destinations you currently have in Airbyte. To do this, follow these steps [^1^]: 1. Decide which connectors you'd like to use. 2. Find the Docker image name of those connectors. Look [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-config-oss/init-oss/src/main/resources/seed/source_definitions.yaml) for sources and [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-config-oss/init-oss/src/main/resources/seed/destination_definitions.yaml) for destinations. 3. For each of the connectors you'd like to use, run docker pull <repository>:<tag>
in your shell, replacing <repository>
and <tag>
with the values copied from the step above. 4. Once you've finished downloading all the images, from the Airbyte repository root, run docker compose down -v
followed by docker compose up
. If the above workaround does not fix your problem, please report it [here](https://github.com/airbytehq/airbyte/issues/1462) or in the [Airbyte Slack](https://slack.airbyte.io). [^1^]: https://docs.airbyte.com/troubleshooting/new-connection