https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> got ```error pulling image Error re...
# ask-ai
m
@kapa.ai got
Copy code
error pulling image Error response from daemon: manifest for airbyte/webapp:1.7.2 not found: manifest unknown: manifest unknown
  DEBUG   error pulling image Error response from daemon: manifest for airbyte/async-profiler:1.7.2 not found: manifest unknown: manifest unknown
k
The error message:
Copy code
error pulling image Error response from daemon: manifest for airbyte/webapp:1.7.2 not found: manifest unknown: manifest unknown DEBUG   error pulling image Error response from daemon: manifest for airbyte/async-profiler:1.7.2 not found: manifest unknown: manifest unknown
means that Docker is unable to find the specified images (
airbyte/webapp:1.7.2
and 
airbyte/async-profiler:1.7.2
) in the registry it is trying to pull from. This is a common issue if: - The image tag does not exist in the Docker registry (for example, on Docker Hub). - There is a typo in the image name or tag. - The Airbyte release for that version has not published those images yet. This issue has been reported by other users as well, especially for the 
airbyte/async-profiler
image, where the expected tag was not available in Docker Hub, causing the installation to hang or fail. In such cases, users have confirmed that the tag simply does not exist for the image in question, and there is no workaround except to wait for the image to be published or to use a different Airbyte version where all required images are available. You can check the available tags for an image directly on [Docker Hub](https://hub.docker.com/u/airbyte) or by using the Docker CLI. If you are following the official documentation and encounter this error, it is likely a problem with the release process or a missing image in the registry. You may want to: - Try installing a different Airbyte version (for example, downgrade to a previous version where the images are available). - Monitor the [Airbyte GitHub issues](https://github.com/airbytehq/airbyte/issues/61339) for updates or similar reports. - If the issue persists, consider opening a new issue with details about your environment and the exact error message. There is no indication in the knowledge sources of a workaround other than switching to a version where all images are present, or waiting for the missing images to be published by the Airbyte team. This is a known issue and has affected other users as well [Docs: Having issue in local setup](https://github.com/airbytehq/airbyte/issues/61339).
m
@kapa.ai how to down grade
k
A message from kapa.ai
To downgrade Airbyte, you generally need to: 1. Stop your current Airbyte instance. 2. Replace your Airbyte deployment files (such as Docker images, Helm chart version, or abctl configuration) with those from the previous version you want to use. 3. Start Airbyte again. For Docker Compose: - Change the version numbers in your 
.env
file and 
docker-compose.yaml
to the desired (older) version. - Run 
docker-compose down
to stop the current instance. - Pull the images for the older version and start Airbyte:
Copy code
docker-compose pull   docker-compose up -d
For abctl: - The knowledge sources indicate that 
abctl
does not provide a direct way to install a specific version of Airbyte. However, you can specify a 
values.yaml
file with the desired version and run:
Copy code
abctl local install --values ./values.yaml
In the 
values.yaml
, configure the Airbyte platform version you want to use. This is the only way mentioned to control the version with 
abctl
[Support QA](#). Important Notes: - Always use the same Airbyte version for both source and target if you are migrating or restoring data, as mismatched versions can cause issues [How to import/export Airbyte to a new instance (docker to docker deploy)](https://discuss.airbyte.io/t/3514). - Downgrading may not always be seamless, especially if there are database schema changes between versions. If you need more detailed, step-by-step instructions for your specific deployment method, please specify whether you are using Docker Compose, Kubernetes, or abctl. If you encounter issues after downgrading, you may need to restore your Airbyte database from a backup taken before the upgrade, as newer versions may have made changes incompatible with older versions. The knowledge sources do not provide detailed downgrade procedures for all deployment types, so proceed with caution.
m
@kapa.ai i want to instal older version of abctl
k
A message from kapa.ai
To install an older version of abctl, you can download a previous release directly from the [abctl GitHub releases page](https://github.com/airbytehq/abctl/releases/). Select the version you want, download the appropriate binary for your operating system and architecture, and follow the manual installation steps provided in the documentation. This process is supported and referenced in the official troubleshooting resources for Airbyte deployments [Documentation: Troubleshooting abctl](https://docs.airbyte.com/platform/1.6/deploying-airbyte/troubleshoot-deploy#additional-resources). Summary of steps: 1. Go to the [abctl releases page](https://github.com/airbytehq/abctl/releases/). 2. Download the release that matches your OS and architecture. 3. Extract the archive (if needed). 4. Move the 
abctl
executable to a directory in your 
PATH
(e.g., 
/usr/local/bin
on Linux/Mac). 5. Verify the installation with:
Copy code
abctl version
This method works for Mac, Linux, and Windows. If you need detailed, OS-specific instructions, let me know!
Open in Slack
PreviousNext
Powered by