Error response from daemon: manifest for airbyte/bootloader:dev not found: manifest unknown: manifest unknown

Sorry @Khuê Lê Hữu, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! 🧑‍💻 Perhaps try again in 5mins?

Error response from daemon: manifest for airbyte/bootloader:dev not found: manifest unknown: manifest unknown

@kapa.ai Error response from daemon: manifest for airbyte/bootloader:dev not found: manifest unknown: manifest unknown

The error message you're seeing typically occurs when Docker is unable to find the specified image on Docker Hub. In this case, it seems like Docker is unable to find the

airbyte/bootloader:dev

image. From the information provided in the extracts, it's not clear why this specific error is occurring. However, there are a few general troubleshooting steps you can take: 1. Check your internet connection: Ensure that your machine has a stable internet connection. Docker needs to connect to Docker Hub to pull the image. 2. Check the image name: Ensure that the image name is spelled correctly. In this case, it should be

airbyte/bootloader:dev

. 3. Check Docker Hub: Visit Docker Hub and check if the

airbyte/bootloader:dev

image exists. If it doesn't, that's likely the cause of the error. 4. Update Airbyte: If you're using an older version of Airbyte, updating to the latest version might resolve the issue. According to the [release notes](https://docs.airbyte.com/release_notes/january_2023), Airbyte v0.40.27 to v0.40.32 includes improvements to the Connector Builder's conversion of YAML manifest to UI form values, which might be relevant to your issue. If none of these steps resolve the issue, I recommend reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io) or opening a Github ticket for further assistance.