Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> Is there an existing issue where airbyte sync marked as succeeded even though docker image for the source is not available

Based on the provided sources, there is **no documented case** where an Airbyte sync *succeeds* when the required Docker image for the source is not available.  What we *do* see is the opposite behavior:  - When a required image is missing, checks/syncs **fail** with errors such as `Could not find image: airbyte/source-postgres:0.4.30`. [[Unable to get image](<https://discuss.airbyte.io/t/1803>)][[S3 destination image not found](<https://discuss.airbyte.io/t/997>)] - In Kubernetes/kind environments, if the image is not loaded into the cluster, you must manually load it with:   ```bash   kind load docker-image &lt;image-name&gt;:&lt;image-tag&gt; -n airbyte-abctl   ```   or the connector will not run. [[Custom connectors kind](<https://docs.airbyte.com/platform/operator-guides/using-custom-connectors#loading-connector-docker-containers-into-kind>)]  There is an open issue about a sync appearing “successful” while not actually moving data, but in that case **all images are present**; the logs explicitly show valid source, destination, and orchestrator images. [[MySQL source success but not](<https://github.com/airbytehq/airbyte/issues/68104>)]  So, from the available information:  - There **is** an issue where syncs show success but aren’t truly successful, **not** related to missing images. - There is **no evidence** in these sources of an issue where a sync completes successfully when the source Docker image is missing.

I couldn’t find any report in the provided sources where:  &gt; the **sync is marked as succeeded** even though the **Docker image for the source is not available**.  What *is* documented is that when the source image is missing, the job **fails** with a clear error like:  &gt; `Could not find image: airbyte/source-postgres:0.4.30` [[Unable to get image](<https://discuss.airbyte.io/t/1803>)]  In that thread, the check/sync does **not** succeed; it errors out as soon as Airbyte can’t pull or find the image. [[Unable to get image](<https://discuss.airbyte.io/t/1803>)]  There is a different open issue where a MySQL sync is marked successful but moves no data, yet in that case all required images (source, destination, orchestrator) are present and correctly launched. [[Mysql source success but not](<https://github.com/airbytehq/airbyte/issues/68104>)]  So, based only on these knowledge sources:  - Yes, there’s an issue about “successful but effectively empty” syncs, **not** tied to missing images. - I’m not seeing any documented issue where a sync is marked as succeeded **because** the source Docker image is missing.