in the new airbyte 1.0 local installation, it hangs when adding connector via docker. The image is stored in artifact registry and airbyte is installed in google vm. Note that the same image can be accessed from previous version of airbyte

Based on the information provided, it seems like you're having trouble adding a connector via Docker in the new Airbyte 1.0 local installation. Here are a few steps you can take to troubleshoot this issue: 1. Check your Docker Registry: Airbyte needs to pull its Docker images from a remote Docker registry to consume a connector. Make sure your custom connectors image is hosted on a private Docker registry. Since you're using Google Cloud, you can use the Artifact Registry. Here's a [quickstart guide](https://cloud.google.com/artifact-registry/docs/docker/quickstart) to help you set it up if you haven't already. 2. Load the Docker Image into the Cluster: If you're running Airbyte in kind (Kubernetes in Docker), you must load the Docker image of the connector into the cluster. You can do this using the following command:

kind load docker-image <image-name>:<image-tag> -n airbyte-abctl

Replace

<image-name>

and

<image-tag>

with the name and tag of your Docker image. 3. Check for Errors: If you're seeing an error like "Get Spec Job Failed" when trying to add the connector, it could mean that the Docker image has not been properly loaded into the cluster. Make sure you've followed the steps above correctly. 4. Upgrade to the Latest Version: If you're using an old version of Airbyte, consider upgrading to the latest version. There was a [Github issue](https://github.com/airbytehq/airbyte/issues/25042) where a similar problem was reported with an old version of Airbyte, and the issue was resolved by upgrading. If you're still having trouble after following these steps, consider reaching out to the Airbyte community on their [discussion forum](https://discuss.airbyte.io/) for further assistance.

@kapa.ai - I deployed Airbyte 1.0 in Google VM and the image can be accessed to an old version of Airbyte (from a different VM). It is only in the new airbyte 1.0 that the image have problems.

Based on the information provided, it seems like you're having trouble accessing the new version of Airbyte on your Google VM. Here are a few steps you can take to troubleshoot this issue: 1. Check the logs: You can use the

docker logs

command to check the logs of your Airbyte server. This might give you more information about what's going wrong. For example, you can run

$ docker logs airbyte-server

to check the server logs ([source](https://discuss.airbyte.io/t/2366)). 2. Upgrade to the latest version: If you're not already using the latest version of Airbyte, you might want to consider upgrading. You can find instructions on how to do this in the [Airbyte documentation](https://docs.airbyte.com/operator-guides/upgrading-airbyte/#upgrading-on-docker) ([source](https://discuss.airbyte.io/t/2366)). 3. Reach out to the community: If you're still having trouble, you might want to reach out to the Airbyte community on [Slack](https://slack.airbyte.com/). They might be able to provide more specific help based on your situation ([source](https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine#troubleshooting)). Remember, it's important to ensure that you're using the same version of Airbyte when transferring an instance from one VM to another ([source](https://discuss.airbyte.io/t/3514)). If none of these steps help, please provide more details about the specific problems you're encountering so we can provide more targeted assistance.