issue: unable to pull mssql image details:2024-05-29 152940 [46mplatform[0m > Docker volume job log path: /tmp/workspace/ba36dcdc-283b-497f-8c14-35fca5556ac1/0/logs.log 2024-05-29 152940 [46mplatform[0m > Executing worker wrapper. Airbyte version: 0.60.1 2024-05-29 152940 [46mplatform[0m > Attempt 0 to save workflow id for cancellation 2024-05-29 152940 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0' 2024-05-29 152940 [46mplatform[0m > 2024-05-29 152940 [46mplatform[0m > ----- START CHECK ----- 2024-05-29 152940 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: '2.0' 2024-05-29 152940 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1' 2024-05-29 152940 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: '0.1' 2024-05-29 152940 [46mplatform[0m > 2024-05-29 152940 [46mplatform[0m > Checking if airbyte/source-mssql:4.0.24 exists... 2024-05-29 152940 [46mplatform[0m > airbyte/source-mssql:4.0.24 not found locally. Attempting to pull the image... 2024-05-29 152940 [46mplatform[0m > Image does not exist. 2024-05-29 152940 [46mplatform[0m > Unexpected error while checking connection: io.airbyte.workers.exception.WorkerException: Could not find image: airbyte/source-mssql:4.0.24

It looks like you are encountering an issue where the Airbyte worker is unable to pull the

airbyte/source-mssql:4.0.24

image. This issue is similar to other issues reported where Airbyte fails to find and pull the required Docker images for connectors. ### Steps to Troubleshoot and Resolve 1. Verify Image Availability: Ensure that the

airbyte/source-mssql:4.0.24

image is available in the Docker registry. You can do this by manually trying to pull the image using the following command:

shell    docker pull airbyte/source-mssql:4.0.24

If the image is not available, you might need to check if there is a typo in the image name or tag, or if the image has been removed or renamed. 2. Check Network Connectivity: Ensure that the machine running Airbyte has internet access and can reach the Docker registry. Network issues can sometimes prevent Docker from pulling images. 3. Update Airbyte Version: Sometimes, updating to the latest version of Airbyte can resolve issues related to image pulling. You are currently using Airbyte version

0.60.1

. Check if there is a newer version available and update if necessary. 4. Logs and Error Messages: Review the logs for any additional error messages that might provide more context. The relevant log output you provided shows:

shell    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

### Similar Issues for Reference - [Issue 36732](https://github.com/airbytehq/airbyte/issues/36732): Similar problem with the

airbyte/source-sftp:0.2.2

image. - [Issue 30575](https://github.com/airbytehq/airbyte/issues/30575): Similar problem with the

airbyte/destination-postgres:0.4.0

image. - [Issue 35704](https://github.com/airbytehq/airbyte/issues/35704): Similar problem with the

airbyte/source-db2:0.2.2

image. These issues indicate that the problem might be related to the availability of the image in the Docker registry or network connectivity issues. If the problem persists, you might want to raise a new issue on the [Airbyte GitHub repository](https://github.com/airbytehq/airbyte/issues) with detailed logs and steps to reproduce the issue. For more detailed troubleshooting, you can refer to the [Airbyte documentation](https://docs.airbyte.com/). If you need further assistance, feel free to ask!

@kapa.ai I can pull the image manually but still getting the same error

It sounds like you're encountering an issue where Airbyte is unable to pull the Docker image automatically, even though you can pull it manually. This is a common issue and can be related to several factors, including Docker configuration and Airbyte's handling of custom connectors. Here are some steps and considerations based on the information from the knowledge sources: 1. Docker Configuration: - Ensure that Docker is properly configured and has enough disk space. This was a common issue mentioned in the forum posts ([source](https://discuss.airbyte.io/t/1803)). - If you are using Docker Desktop with WSL2, make sure it is enabled and has sufficient resources allocated ([source](https://discuss.airbyte.io/t/1803)). 2. Manual Pulling of Images: - If you can pull the image manually but Airbyte still cannot find it, it might be due to the image not being available in the expected location or format. Ensure that the image is tagged correctly and available locally ([source](https://discuss.airbyte.io/t/997)). 3. Custom Connectors: - When adding a custom source, make sure you are using the full repository URL for the image name and the specific tag as pushed to your private repository. This was highlighted in the forum post about custom sources ([source](https://discuss.airbyte.io/t/3958)). - If you are running the instance on a different machine than where you built the connector, try pulling the image manually on the target machine ([source](https://github.com/airbytehq/airbyte/issues/35238)). 4. ARM64 Compatibility: - If you are running on an ARM64 architecture, ensure that the image is built for ARM64. This was a solution for a similar issue where the image needed to be built for ARM64 to work ([source](https://github.com/airbytehq/airbyte/issues/35238)). 5. Reinstallation: - As a last resort, you might want to try a complete reinstallation of Docker Desktop. This has worked for other users facing similar issues ([source](https://discuss.airbyte.io/t/1803)). If these steps do not resolve your issue, you might want to check the detailed error logs from Airbyte to get more insights into what might be going wrong. You can also refer to the [Airbyte documentation](https://docs.airbyte.com) for more detailed troubleshooting steps. If you need further assistance, please provide more details about your setup and the specific error messages you are encountering.

@kapa.ai Message: HikariPool-1 - Connection is not available, request timed out after 60005ms (total=0, active=0, idle=0, waiting=0)

A message from kapa.ai

@kapa.ai Postgres destination fails to connect with the following 2024-05-30 204854 [46mplatform[0m > Docker volume job log path: /tmp/workspace/1977be82-741c-4f8e-8616-ffa0bd848965/0/logs.log 2024-05-30 204854 [46mplatform[0m > Executing worker wrapper. Airbyte version: 0.60.1 2024-05-30 204854 [46mplatform[0m > Attempt 0 to save workflow id for cancellation 2024-05-30 204854 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0' 2024-05-30 204854 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: '2.0' 2024-05-30 204854 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1' 2024-05-30 204854 [46mplatform[0m > 2024-05-30 204854 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: '0.1' 2024-05-30 204854 [46mplatform[0m > ----- START CHECK ----- 2024-05-30 204854 [46mplatform[0m > 2024-05-30 204854 [46mplatform[0m > Checking if airbyte/destination-postgres:2.0.10 exists... 2024-05-30 204854 [46mplatform[0m > airbyte/destination-postgres:2.0.10 was found locally. 2024-05-30 204854 [46mplatform[0m > Creating docker container = destination-postgres-check-1977be82-741c-4f8e-8616-ffa0bd848965-0-gpsxd with resources io.airbyte.config.ResourceRequirements@efb701b[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=,additionalProperties={}] and allowedHosts null 2024-05-30 204854 [46mplatform[0m > Preparing command: docker run --rm --init -i -w /data/1977be82-741c-4f8e-8616-ffa0bd848965/0 --log-driver none --name destination-postgres-check-1977be82-741c-4f8e-8616-ffa0bd848965-0-gpsxd --network host -v airbyte_workspace:/data -v oss_local_root:/local -e DEPLOYMENT_MODE=OSS -e WORKER_CONNECTOR_IMAGE=airbyte/destination-postgres:2.0.10 -e AUTO_DETECT_SCHEMA=true -e LAUNCHDARKLY_KEY= -e SOCAT_KUBE_CPU_REQUEST=0.1 -e SOCAT_KUBE_CPU_LIMIT=2.0 -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE=dev -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e OTEL_COLLECTOR_ENDPOINT=http://host.docker.internal:4317 -e FEATURE_FLAG_CLIENT=config -e AIRBYTE_VERSION=0.60.1 -e WORKER_JOB_ID=1977be82-741c-4f8e-8616-ffa0bd848965 airbyte/destination-postgres:2.0.10 check --config source_config.json 2024-05-30 204854 [46mplatform[0m > Reading messages from protocol version 0.2.0 2024-05-30 204855 [46mplatform[0m > INFO main i.a.i.d.p.PostgresDestination(main):169 starting destination: class io.airbyte.integrations.destination.postgres.PostgresDestination 2024-05-30 204855 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationCliParser$Companion(parseOptions):145 integration args: {check=null, config=source_config.json} 2024-05-30 204855 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationRunner(runInternal):124 Running integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedDestination 2024-05-30 204855 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationRunner(runInternal):125 Command: CHECK 2024-05-30 204855 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationRunner(runInternal):126 Integration config: IntegrationConfig{command=CHECK, configPath='source_config.json', catalogPath='null', statePath='null'} 2024-05-30 204856 [46mplatform[0m > WARN main c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword 2024-05-30 204856 [46mplatform[0m > INFO main i.a.c.i.b.s.SshTunnel$Companion(getInstance):428 Starting connection with method: NO_TUNNEL 2024-05-30 204856 [46mplatform[0m > INFO main c.z.h.HikariDataSource(<init>):79 HikariPool-1 - Starting... 2024-05-30 204856 [46mplatform[0m > INFO main c.z.h.HikariDataSource(<init>):81 HikariPool-1 - Start completed. 2024-05-30 204956 [46mplatform[0m > INFO main c.z.h.HikariDataSource(close):349 HikariPool-1 - Shutdown initiated... 2024-05-30 204956 [46mplatform[0m > INFO main c.z.h.HikariDataSource(close):351 HikariPool-1 - Shutdown completed. 2024-05-30 204956 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationRunner(runInternal):251 Completed integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedDestination 2024-05-30 204956 [46mplatform[0m > INFO main i.a.i.d.p.PostgresDestination(main):171 completed destination: class io.airbyte.integrations.destination.postgres.PostgresDestination 2024-05-30 204956 [46mplatform[0m > Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@60ea2fb4[status=failed,message=State code: 08001; Message: The connection attempt failed.,additionalProperties={}] 2024-05-30 204956 [46mplatform[0m > 2024-05-30 204956 [46mplatform[0m > ----- END CHECK ----- 2024-05-30 204956 [46mplatform[0m >

A message from kapa.ai

@kapa.ai Postgres destination fails with following error: 2024-05-30 204854 [46mplatform[0m > Docker volume job log path: /tmp/workspace/1977be82-741c-4f8e-8616-ffa0bd848965/0/logs.log 2024-05-30 204854 [46mplatform[0m > Executing worker wrapper. Airbyte version: 0.60.1 2024-05-30 204854 [46mplatform[0m > Attempt 0 to save workflow id for cancellation 2024-05-30 204854 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0' 2024-05-30 204854 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: '2.0' 2024-05-30 204854 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1' 2024-05-30 204854 [46mplatform[0m > 2024-05-30 204854 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: '0.1' 2024-05-30 204854 [46mplatform[0m > ----- START CHECK ----- 2024-05-30 204854 [46mplatform[0m > 2024-05-30 204854 [46mplatform[0m > Checking if airbyte/destination-postgres:2.0.10 exists... 2024-05-30 204854 [46mplatform[0m > airbyte/destination-postgres:2.0.10 was found locally. 2024-05-30 204854 [46mplatform[0m > Creating docker container = destination-postgres-check-1977be82-741c-4f8e-8616-ffa0bd848965-0-gpsxd with resources io.airbyte.config.ResourceRequirements@efb701b[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=,additionalProperties={}] and allowedHosts null 2024-05-30 204854 [46mplatform[0m > Preparing command: docker run --rm --init -i -w /data/1977be82-741c-4f8e-8616-ffa0bd848965/0 --log-driver none --name destination-postgres-check-1977be82-741c-4f8e-8616-ffa0bd848965-0-gpsxd --network host -v airbyte_workspace:/data -v oss_local_root:/local -e DEPLOYMENT_MODE=OSS -e WORKER_CONNECTOR_IMAGE=airbyte/destination-postgres:2.0.10 -e AUTO_DETECT_SCHEMA=true -e LAUNCHDARKLY_KEY= -e SOCAT_KUBE_CPU_REQUEST=0.1 -e SOCAT_KUBE_CPU_LIMIT=2.0 -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE=dev -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e OTEL_COLLECTOR_ENDPOINT=http://host.docker.internal:4317 -e FEATURE_FLAG_CLIENT=config -e AIRBYTE_VERSION=0.60.1 -e WORKER_JOB_ID=1977be82-741c-4f8e-8616-ffa0bd848965 airbyte/destination-postgres:2.0.10 check --config source_config.json 2024-05-30 204854 [46mplatform[0m > Reading messages from protocol version 0.2.0 2024-05-30 204855 [46mplatform[0m > INFO main i.a.i.d.p.PostgresDestination(main):169 starting destination: class io.airbyte.integrations.destination.postgres.PostgresDestination 2024-05-30 204855 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationCliParser$Companion(parseOptions):145 integration args: {check=null, config=source_config.json} 2024-05-30 204855 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationRunner(runInternal):124 Running integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedDestination 2024-05-30 204855 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationRunner(runInternal):125 Command: CHECK 2024-05-30 204855 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationRunner(runInternal):126 Integration config: IntegrationConfig{command=CHECK, configPath='source_config.json', catalogPath='null', statePath='null'} 2024-05-30 204856 [46mplatform[0m > WARN main c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword 2024-05-30 204856 [46mplatform[0m > INFO main i.a.c.i.b.s.SshTunnel$Companion(getInstance):428 Starting connection with method: NO_TUNNEL 2024-05-30 204856 [46mplatform[0m > INFO main c.z.h.HikariDataSource(<init>):79 HikariPool-1 - Starting... 2024-05-30 204856 [46mplatform[0m > INFO main c.z.h.HikariDataSource(<init>):81 HikariPool-1 - Start completed. 2024-05-30 204956 [46mplatform[0m > INFO main c.z.h.HikariDataSource(close):349 HikariPool-1 - Shutdown initiated... 2024-05-30 204956 [46mplatform[0m > INFO main c.z.h.HikariDataSource(close):351 HikariPool-1 - Shutdown completed. 2024-05-30 204956 [46mplatform[0m > INFO main i.a.c.i.b.IntegrationRunner(runInternal):251 Completed integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedDestination 2024-05-30 204956 [46mplatform[0m > INFO main i.a.i.d.p.PostgresDestination(main):171 completed destination: class io.airbyte.integrations.destination.postgres.PostgresDestination 2024-05-30 204956 [46mplatform[0m > Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@60ea2fb4[status=failed,message=State code: 08001; Message: The connection attempt failed.,additionalProperties={}] 2024-05-30 204956 [46mplatform[0m > 2024-05-30 204956 [46mplatform[0m > ----- END CHECK ----- 2024-05-30 204956 [46mplatform[0m >

A message from kapa.ai

@kapa.ai whats wrong kapa?

A message from kapa.ai