Summary
When trying to reference a locally stored Docker image in airbyte-ci, the system still attempts to resolve the image from docker.io. User is seeking advice on how to resolve this issue.
Question
Hi everyone,
http://Kapa.ai|Kapa.ai suggested that when running airbyte-ci or airbyte-ci-dev locally, you can indeed reference a Docker image that you have locally on your machine. For example, if you have a Docker image tagged as my-custom-image:tag, you can set baseImage to my-custom-image:tag.
Example:
baseImage: ssl-python-connector-base:dev```
So, I tried the above, but seems like it still tries to resolve Image from <http://docker.io|docker.io>:
```│ │ █ [0.31s] ERROR from(address: "ssl-python-connector-base:dev")
│ │ ┣─╮
│ │ │ ▽ from ssl-python-connector-base:dev
│ │ │ █ [0.31s] ERROR resolve image config for docker.io/library/ssl-python-connector-base:dev```
Could you please advise?
<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/p1722128155552379) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["airbyte-ci", "docker-image", "connectorbuildoptions", "baseimage", "local-image"]
</sub>