I’m getting this error after updating the airbyte on docker

service "bootloader" didn't complete successfully: exit 255

Any idea how to fix it?

airbyte-db                        | 2023-07-26 15:46:16.823 UTC [86] ERROR:  relation "public.actor_definition_version" does not exist at character 342
airbyte-db                        | 2023-07-26 15:46:16.823 UTC [86] STATEMENT:  select distinct "public"."actor_definition"."id", "public"."actor_definition_version"."docker_repository", "public"."actor_definition"."actor_type", "public"."actor_definition_version"."protocol_version" from "public"."actor_definition" join "public"."actor" on "public"."actor"."actor_definition_id" = "public"."actor_definition"."id" join "public"."actor_definition_version" on "public"."actor_definition_version"."id" = "public"."actor_definition"."default_version_id"
airbyte-bootloader                | 2023-07-26 15:46:16 ERROR i.a.b.Application(main):25 - Unable to bootstrap Airbyte environment.
airbyte-bootloader                | org.jooq.exception.DataAccessException: SQL [select distinct "public"."actor_definition"."id", "public"."actor_definition_version"."docker_repository", "public"."actor_definition"."actor_type", "public"."actor_definition_version"."protocol_version" from "public"."actor_definition" join "public"."actor" on "public"."actor"."actor_definition_id" = "public"."actor_definition"."id" join "public"."actor_definition_version" on "public"."actor_definition_version"."id" = "public"."actor_definition"."default_version_id"]; ERROR: relation "public.actor_definition_version" does not exist

Based on the information provided in the extracts, it seems like you're encountering an error due to a missing table in your database, specifically the "public.actor_definition_version" table. This could be due to an unsuccessful or incomplete upgrade process. One of the users in a [previous support conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1674463634901159) encountered a similar issue after updating Airbyte. The user was able to resolve the issue by checking the

actor_definition

table in the Airbyte database and ensuring that none of the connections had the tag 'latest'. Here's how you can check your

actor_definition

table:

sql select * from actor_definition where actor_definition.docker_repository like '%latest';

If any records are returned, you'll need to update them to use a specific version instead of 'latest'. However, this might not be the exact solution to your problem as your error message indicates a missing table, not an invalid version string. If the issue persists, it might be necessary to perform a clean installation of Airbyte or reach out to the Airbyte support for further assistance. Please note that this advice is based on the information available in the provided extracts and might not completely solve your issue.