Airbyte-bootloader container failing to boot Airbyte

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is experiencing issues with the airbyte-bootloader container failing to boot Airbyte. They are seeking assistance in identifying the possible reasons for this failure.


Question

Container airbyte-bootloader is failing when we are trying to boot the airbyte.

what could be the reason?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["airbyte-bootloader", "container", "boot", "failure"]
2

Check the logs for that deployment. Failures at that stage almost always relate to configuration issues (E.g. missing values, duplicate environment vars due to incorrect config, etc.)

3

Now the new error post booting is

{
  "i18nKey": "errors.http.badGateway",
  "i18nParams": {
    "status": 502
  },
  "name": "HttpError",
  "requestId": "k9DauyxKdbvvDnA6sUtijV",
  "request": {
    "url": "/api/v1/instance_configuration",
    "method": "get"
  },
  "status": 502,
  "response": "<!DOCTYPE html>\n&lt;html&gt;\n&lt;head&gt;\n&lt;title&gt;Error&lt;/title&gt;\n&lt;style&gt;\nhtml { color-scheme: light dark; }\nbody { width: 35em; margin: 0 auto;\nfont-family: Tahoma, Verdana, Arial, sans-serif; }\n&lt;/style&gt;\n&lt;/head&gt;\n&lt;body&gt;\n&lt;h1&gt;An error occurred.&lt;/h1&gt;\n&lt;p&gt;Sorry, the page you are looking for is currently unavailable.&lt;br/&gt;\nPlease try again later.&lt;/p&gt;\n&lt;p&gt;If you are the system administrator of this resource then you should check\nthe error log for details.&lt;/p&gt;\n&lt;p&gt;&lt;em&gt;Faithfully yours, nginx.&lt;/em&gt;&lt;/p&gt;\n&lt;/body&gt;\n&lt;/html&gt;\n"
}```
4

yeah, I’m guessing it bootloader failed that the rest of the deployment didn’t come up healthy.

How are you deploying Airbyte? (abctl, Helm, etc.)

5

docker compose on google vm

6

Ok, so I did not do anything and it came back up

7

There is something wrong for sure with latest build

8

Gotcha, was likely still initializing the other containers.

You can sometimes find related issues with docker-compose logs

You can also check the individual container logs (e.g. for bootloader) as they may have additional details