Error connecting to OpenWeather source in Airbyte

Summary

When setting up the connection to OpenWeather in Airbyte locally via Docker Compose on MacOS, encountering an error where the image airbyte/source-openweather:0.2.7 cannot be found. Even after trying to pull the image with ‘docker pull’, the issue persists.


Question

Hey! I’m trying to setup a connection to OpenWeather, but I think I’m making some rookie mistakes here…

I’m running Airbyte locally via Docker Compose on MacOS. When setting up the connection, I’m getting this error log:

2024-07-01 17:52:10 platform > Executing worker wrapper. Airbyte version: 0.63.3
2024-07-01 17:52:10 platform > 
2024-07-01 17:52:10 platform > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0'
2024-07-01 17:52:10 platform > ----- START CHECK -----
2024-07-01 17:52:10 platform > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: '2.0'
2024-07-01 17:52:10 platform > 
2024-07-01 17:52:10 platform > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1'
2024-07-01 17:52:10 platform > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: '0.1'
2024-07-01 17:52:10 platform > Checking if airbyte/source-openweather:0.2.7 exists...
2024-07-01 17:52:10 platform > airbyte/source-openweather:0.2.7 not found locally. Attempting to pull the image...
2024-07-01 17:52:10 platform > Image does not exist.
2024-07-01 17:52:10 platform > Unexpected error while checking connection: 
io.airbyte.workers.exception.WorkerException: Could not find image: airbyte/source-openweather:0.2.7
	at io.airbyte.workers.process.DockerProcessFactory.create(DockerProcessFactory.java:117) ~[io.airbyte-airbyte-commons-worker-0.63.3.jar:?]
	at io.airbyte.workers.process.AirbyteIntegrationLauncher.check(AirbyteIntegrationLauncher.java:147) ~[io.airbyte-airbyte-commons-worker-0.63.3.jar:?]
	at io.airbyte.workers.general.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:71) ~[io.airbyte-airbyte-commons-worker-0.63.3.jar:?]
	at io.airbyte.workers.general.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:44) ~[io.airbyte-airbyte-commons-worker-0.63.3.jar:?]
	at io.airbyte.workers.temporal.TemporalAttemptExecution.get(TemporalAttemptExecution.java:138) ~[io.airbyte-airbyte-workers-0.63.3.jar:?]
	at io.airbyte.workers.temporal.check.connection.CheckConnectionActivityImpl.lambda$runWithJobOutput$1(CheckConnectionActivityImpl.java:227) ~[io.airbyte-airbyte-workers-0.63.3.jar:?]
	at io.airbyte.commons.temporal.HeartbeatUtils.withBackgroundHeartbeat(HeartbeatUtils.java:57) ~[io.airbyte-airbyte-commons-temporal-core-0.63.3.jar:?]
	at io.airbyte.workers.temporal.check.connection.CheckConnectionActivityImpl.runWithJobOutput(CheckConnectionActivityImpl.java:212) ~[io.airbyte-airbyte-workers-0.63.3.jar:?]```
I get that it's not finding it, but running `docker pull airbyte/source-openweather:0.2.7`  also doesn't solve it.

How can I fix this?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1719856999888179) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["openweather-connector", "docker-compose", "image-not-found", "docker-pull"]
</sub>

are you logged into http://hub.docker.com|hub.docker.com in your Docker Desktop and have Allow the default Docker socket to be used (requires password) setting enabled?

It is turned on on my side:

Does the System/User maybe cause the issue?

you can try to change it

what version of Docker Desktop do you have?

I had older version 4.26.0. I upgraded and I’m checking on 4.31.0.

I’d guess that the version is not the issue

it’s pulling image, so yeah, version of Docker Desktop is not affecting it

I’ll try to reinstall docker

I know it’s probably a setting or something since I’m getting the same error for Airtable. Do I need to open something?

Reinstalling also didn’t help… it’s strange.

<@U07B807PM6C> I rerun the run-ab=platform.sh again and that seemed to fix the issue for me.

I’ll have a look if that works