Issue setting up MSSQL source

Summary

Error encountered while trying to set up MSSQL source, specifically with pulling the image airbyte/source-mssql:4.0.24. Manual image pull did not resolve the problem.


Question

Hi Airbyte community. Run into the following problem when trying to set up a MSSQL source. please see screenshots attached. Can pull the image mssql manually, but that does not resolve the problem. Not sure how to proceed

2024-05-29 15:29:40 [46mplatform[0m > Executing worker wrapper. Airbyte version: 0.60.1
2024-05-29 15:29:40 [46mplatform[0m > Attempt 0 to save workflow id for cancellation
2024-05-29 15:29:40 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0'
2024-05-29 15:29:40 [46mplatform[0m > 
2024-05-29 15:29:40 [46mplatform[0m > ----- START CHECK -----
2024-05-29 15:29:40 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: '2.0'
2024-05-29 15:29:40 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1'
2024-05-29 15:29:40 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: '0.1'
2024-05-29 15:29:40 [46mplatform[0m > 
2024-05-29 15:29:40 [46mplatform[0m > Checking if airbyte/source-mssql:4.0.24 exists...
2024-05-29 15:29:40 [46mplatform[0m > airbyte/source-mssql:4.0.24 not found locally. Attempting to pull the image...
2024-05-29 15:29:40 [46mplatform[0m > Image does not exist.
2024-05-29 15:29:40 [46mplatform[0m > Unexpected error while checking connection: 
io.airbyte.workers.exception.WorkerException: Could not find image: airbyte/source-mssql:4.0.24```

<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/p1716998492515219) if you want 
to access the original thread.

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

<sub>
["mssql-source", "image-pull-error", "airbyte-source-mssql", "connector-setup"]
</sub>

are you behind a proxy by any chance? I had the same issue on 0.59 OSS and solved by adding the docker-proxy service to the no_proxy config.

<@U066U84SC0P> Thank you for your suggestion. I rerun the run-ab=platform.sh again and that seemed to fix the issue.