I am observing:

io.airbyte.workers.exception.WorkerException: Could not find image: airbyte/source-google-analytics-data-api:0.0.3

How can I configure airbyte to work on-premise in a firewalled environment with a corporate docker registry/proxy? I.e. how to tell airbyte to pull from a local Artifactory instance similar to:

<http://local_docker_registry.mycorp.com/airbyte/source-google-analytics-data-api:0.0.3|local_docker_registry.mycorp.com/airbyte/source-google-analytics-data-api:0.0.3>

?

Hi. Did you create a build for the image? if no then run example: :

docker build . -t airbyte/your-source-name:0.1a

In general- this is not an airbyte question but rather a docker question. you need to create\build the image with a tag (for easier life) each time you are updating \ creating new classes so docker will be able to tell the app that it has this and that version and dependencies

I was simply running docker-compose up on the airbyte example. I would expect to be able to reconfigure airbyte to pull from a corporate registry.

running docker compose up simply runs docker while fetching the images that were registered to it - making it auto is possible though I`m not sure airbyte supports this and nor should it in my opinion - since this part is crucial for correct CI\CD If you create CI\CD you can achieve what you are looking for.

Where could the connector images be reconfigured in the docker-compose file? https://github.com/airbytehq/airbyte/blob/master/docker-compose.yaml#L110 is not having any (at least for me obvious) option.

So yes - it`s not an easy one- My solution: https://discuss.airbyte.io/t/python-custom-source-build-internal-server-error-get-spec-job-failed/2248

So you modified some airbyte interla

source_specs

file? This sounds like a fork/source change to me I would really want to have a more native option

@[DEPRECATED] Marcos Marx turned this thread into Zendesk ticket 2610 to ensure timely resolution!

@Georg Heiler today Airbyte won’t pull from private/other registries 😞 you need to pull the image manually to your server

@Marcos Marx (Airbyte) so the only workaround would be to manually pull (and then re-tag the image right?

For now, yes 😞