https://linen.dev logo
Join Slack
Powered by
I am getting the following errors when trying to r...
# ask-ai
g
I am getting the following errors when trying to run 
abctl local install --values ./values.yaml
after upgrading to 1.7.2. Do you have a way to troubleshoot and resolve?
Copy code
airbyte-bootloader: An error occurred on connector rollout object creation                                                                                                                                                          
  ERROR   airbyte-bootloader: An error occurred on connector rollout object creation                                                                                                                                                          
 WARNING  Back-off pulling image "airbyte/webapp:1.7.2"                                                                                                                                                                                       
 WARNING  Back-off pulling image "airbyte/webapp:1.7.2"                                                                                                                                                                                       
 WARNING  Back-off pulling image "airbyte/webapp:1.7.2"                                                                                                                                                                                       
 WARNING  Back-off pulling image "airbyte/webapp:1.7.2"                                                                                                                                                                                       
 WARNING  Back-off pulling image "airbyte/webapp:1.7.2"                                                                                                                                                                                       
 WARNING  Back-off pulling image "airbyte/webapp:1.7.2"                                                                                                                                                                                       
 WARNING  Encountered an issue deploying Airbyte:                                                                                                                                                                                             
            Pod: airbyte-abctl-webapp-cdc89b8bc-zbzml.1854ecf0d90170f4
            Reason: Failed
            Message: Error: ImagePullBackOff
            Count: 6
k
The errors you are seeing—such as repeated "Back-off pulling image" and "Error: ImagePullBackOff" for the Airbyte webapp—indicate that Kubernetes is unable to pull the required Docker images for Airbyte version 1.7.2. Additionally, the "airbyte-bootloader: An error occurred on connector rollout object creation" suggests a failure early in the deployment process. Here are some troubleshooting steps based on the knowledge sources: 1. Check Docker Hub Rate Limits and Authentication If you are hitting Docker Hub pull rate limits, you may see similar errors. Try authenticating Docker with your Docker Hub credentials to increase your pull limits. You can do this with:
Copy code
docker login
Then retry the installation. This issue has been observed in previous Airbyte deployments and can cause "ImagePullBackOff" errors if the rate limit is exceeded [Docker pull rate-limit on abctl local install](https://github.com/airbytehq/airbyte/issues/46309). 2. Check Internet Connectivity and Proxy Settings Ensure your machine has a stable internet connection and can reach Docker Hub. If you are behind a proxy or firewall, make sure it allows access to Docker Hub and the required image repositories. 3. Check Machine Resources Insufficient resources (CPU, RAM) can cause pods to fail to start or pull images. One user resolved similar issues by upgrading their machine size (e.g., to a larger EC2 instance type) [abctl install stuck at pulling images](https://github.com/airbytehq/airbyte/issues/48720). 4. Retry the Installation Sometimes, image pull failures are transient. Simply retrying the installation can resolve the issue if it was a temporary network or Docker Hub issue [abctl install stuck at pulling images](https://github.com/airbytehq/airbyte/issues/48720). 5. Check for Bootloader/Database Connectivity Issues The Airbyte bootloader must connect to the Airbyte database to proceed. If the bootloader fails, check the logs for the Airbyte database pod and ensure it is running and accessible. This is a common cause of bootloader failures [Troubleshooting abctl](https://docs.airbyte.com/platform/1.6/deploying-airbyte/troubleshoot-deploy). 6. Review Service Logs abctl versions >0.15.0 print service logs to help diagnose issues. Review the logs for more specific error messages, especially for the bootloader and webapp pods [Troubleshooting abctl](https://docs.airbyte.com/platform/1.6/deploying-airbyte/troubleshoot-deploy). If you continue to see "ImagePullBackOff" after these steps, try pulling the image manually to see if there are any errors:
Copy code
docker pull airbyte/webapp:1.7.2
If this fails, it may provide more details about the underlying issue. If none of these steps resolve the problem, please provide additional logs or error messages for further assistance.
g
@kapa.ai running 
docker pull airbyte/webapp:1.7.2
return "Error response from daemon: manifest for airbyte/webapp:1.7.2 not found: manifest unknown: manifest unknown" the only docker container that runs is airbyte-abctl-control-plane so I can't look at airbyte-db
k
A message from kapa.ai
The error message you received—`manifest for airbyte/webapp:1.7.2 not found: manifest unknown`—means that the Docker image for 
airbyte/webapp:1.7.2
does not exist in the Docker registry. This is why Kubernetes is unable to pull the image and is resulting in the 
ImagePullBackOff
error during your 
abctl local install
. This situation has been reported by other users as well, where a required image (such as 
airbyte/async-profiler
or other Airbyte images) was not available on Docker Hub for the specified version, causing the installation to hang or fail. In those cases, the only running container was also 
airbyte-abctl-control-plane
, and users could not proceed further or access other Airbyte services like the database pod. The root cause was the missing image in the registry, not a local configuration issue or a problem with your environment [Docs: Having issue in local setup](https://github.com/airbytehq/airbyte/issues/61339). What you can do: - Double-check the Airbyte Docker Hub repository to confirm that the 
webapp:1.7.2
image is indeed missing. - If the image is missing, you will not be able to proceed with this version until the image is published. - Consider downgrading to a previous Airbyte version for which all required images are available, or wait until the Airbyte team publishes the missing image for 1.7.2. Unfortunately, there is no workaround for a missing image except to use a version that is fully published or to contact the Airbyte maintainers to report the missing image and request that it be pushed to the registry. If you need to check which images are required for a specific Airbyte version, you can use:
Copy code
abctl images manifest
This will list all images needed for your deployment, so you can verify their availability before attempting installation [Configure a custom image registry](https://docs.airbyte.com/platform/1.6/enterprise-setup/implementation-guide#configure-a-custom-image-registry). Summary: The installation cannot proceed because the required Docker image 
airbyte/webapp:1.7.2
is not available in the registry. This is a known issue when images are missing for a release, and the only solution is to use a version with all images available or wait for the missing image to be published.
g
@kapa.ai How do I install a different version of airbyte
k
A message from kapa.ai
To install a different version of Airbyte using 
abctl
, you need to specify the desired version in your 
values.yaml
file and then run the install command with that file. The 
abctl
tool itself does not provide a direct flag to select the Airbyte version, but you can control the version through the configuration in `values.yaml`: 1. Edit your 
values.yaml
file Set the desired Airbyte version in the appropriate field (for example, under 
global.image.tag
). 2. Install Airbyte with your custom values file Run:
Copy code
abctl local install --values ./values.yaml
This approach allows you to specify the Airbyte platform version you want to use. If you do not specify a version, 
abctl
will install or upgrade to the latest available version by default [Support QA: How to install a specific version of airbyte using abctl?](#). > Note: > The knowledge sources do not provide an explicit example of the 
values.yaml
content for version selection, but they confirm that version control is managed via the values file and not directly through an 
abctl
flag.
g
@kapa.ai I tried installing 1.7.1 and that is the same. I do see
Copy code
Namespace 'airbyte-abctl' already exists                                                                                                                                                                                            
  INFO    Persistent volume 'airbyte-minio-pv' already exists                                                                                                                                                                                 
  INFO    Persistent volume claim 'airbyte-minio-pv-claim-airbyte-minio-0' already exists                                                                                                                                                     
  INFO    Persistent volume 'airbyte-volume-db' already exists
Are those a big deal or are the purely informational?
k
A message from kapa.ai
The messages like
Copy code
Namespace 'airbyte-abctl' already exists INFO    Persistent volume 'airbyte-minio-pv' already exists INFO    Persistent volume claim 'airbyte-minio-pv-claim-airbyte-minio-0' already exists INFO    Persistent volume 'airbyte-volume-db' already exists
are informational and indicate that these Kubernetes resources were already created in a previous installation attempt. They are not errors by themselves and do not prevent Airbyte from installing or running. These messages are common when re-running 
abctl local install
after a failed or interrupted installation, or when upgrading Airbyte [Migration failing when upgrading with abctl](https://github.com/airbytehq/airbyte/issues/55251). If you continue to encounter installation issues, the root cause is likely elsewhere (such as missing Docker images), not these informational messages.
g
Ok. Specifying the version 1.7.1 seemed to work, however, after initially pulling 1.7.1 images, I received this output
Copy code
Installed Helm Chart airbyte/airbyte:                                                                                                                                                                                               
            Name: airbyte-abctl
            Namespace: airbyte-abctl
            Version: 1.7.2
            AppVersion: 1.7.2
            Release: 4
@kapa.ai Ok. Specifying the version 1.7.1 seemed to work, however, after initially pulling 1.7.1 images, I received this output
Copy code
Installed Helm Chart airbyte/airbyte:                                                                                                                                                                                               
            Name: airbyte-abctl
            Namespace: airbyte-abctl
            Version: 1.7.2
            AppVersion: 1.7.2
            Release: 4
k
A message from kapa.ai
Based on your output, even though you attempted to install Airbyte version 1.7.1, the Helm chart that was actually installed is version 1.7.2:
Copy code
Installed Helm Chart airbyte/airbyte:                                                                                                                                                                                                            Name: airbyte-abctl             Namespace: airbyte-abctl             Version: 1.7.2             AppVersion: 1.7.2             Release: 4
This suggests that the version being installed is determined by the Helm chart version being used, not just the image tags or the version you specify in your 
values.yaml
. The 
abctl
tool and Helm will, by default, use the latest chart version available unless you explicitly specify a chart version. To install a specific version of Airbyte, you need to: 1. Specify the desired Helm chart version using the 
--version
flag when running Helm directly, or ensure your tooling (like 
abctl
) supports passing this version. 2. Make sure your 
values.yaml
(if used) matches the version you want to install. The knowledge sources indicate that when using Helm directly, you can specify the version like this:
Copy code
bash helm upgrade --install <RELEASE-NAME> airbyte/airbyte --values <VALUES.YAML> --version <HELM-APP-VERSION>
or for v2 charts:
Copy code
bash helm upgrade airbyte airbyte-v2/airbyte \   --namespace airbyte-v2 \   --values ./values.yaml \   --version 2.0.3 \   --set global.image.tag=1.7.0
[Upgrading Airbyte on Kubernetes with Helm](https://docs.airbyte.com/platform/next/operator-guides/upgrading-airbyte) With 
abctl
, the knowledge sources do not explicitly state how to pass the Helm chart version, so if you do not specify it, it will use the latest available chart, which may not match the image version you want. Summary: Your installation is using the latest Helm chart (1.7.2), not 1.7.1, likely because the chart version was not explicitly set. To ensure you install a specific version, you must specify both the chart version and the image tag, if your tooling allows. If 
abctl
does not support this, you may need to use Helm directly for precise version control. The knowledge sources do not provide more detailed instructions for version pinning with 
abctl
.
j
I am also facing this same ImagePullBackOff issue on fresh 
abctl local install
. It looks like webapp:1.7.2 should exist on Docker Hub but it is not there.
g
Here is what I did, and I'm unsure if it actually solved something or if it was luck but I run 
abctl local install --values ./values.yaml
where values.yaml has
Copy code
global:
  image:
    tag: 1.7.1
It tried to install 1.7.1 but eventually installed 1.7.2. Give that a go
✅ 1
j
Unfortunately, for me, installing 1.7.1 gives the ImagePullBackOff message for additional images.
Good news on my side, I updated ./values.yaml with 1.7.2 and now everything works, maybe someone uploaded the missing image.
g
Great! Also, that's what I'm wondering. There were definitely errors when I would check docker hub form the command line.
5 Views
Open in Slack
PreviousNext
Powered by