A S Yamini
12/08/2025, 1:28 PMkapa.ai
12/08/2025, 1:28 PMairbyte-db pod cannot start because the mounted data directory has the wrong owner/permissions. This causes the bootloader to fail since it can’t connect to the database. [[Perm issue abctl](https://github.com/airbytehq/airbyte/issues/54199); [Perm issue Colima](https://github.com/airbytehq/airbyte/issues/54995)] For abctl local install, the Postgres data is under your local Airbyte directory, typically: bash ~/.airbyte/abctl/data/airbyte-volume-db From the linked issues, users have fixed this by adjusting ownership/permissions of that directory on the host so they match what Postgres expects inside the container: 1. On Linux VMs (including Ubuntu, GCE): bash # 70 is the UID used by the Postgres container sudo chown -R 70:70 ~/.airbyte/abctl/data/airbyte-volume-db [[Perm issue abctl](https://github.com/airbytehq/airbyte/issues/62093)] 2. If you still get permission errors, ensure your user can traverse/read the directory (example from a GCE VM): bash sudo setfacl -m u:$USER:x ~/.airbyte/abctl/data/airbyte-volume-db/pgdata sudo setfacl -m u:$USER:r ~/.airbyte/abctl/data/airbyte-volume-db/pgdata/PG_VERSION [[Perm issue abctl](https://github.com/airbytehq/airbyte/issues/62093)] After fixing ownership/ACLs: bash abctl local uninstall # optional but recommended to clean stuck resources abctl local install If you are running under Colima or another non-Docker Desktop runtime, the same directory-ownership issue applies; ensure the mounted path is writable by UID 70 and that `chown`/`chmod` inside the container are allowed. [[Perm issue Colima](https://github.com/airbytehq/airbyte/issues/54995)] If you still see wrong ownership or operation not permitted on that path after doing the above, the knowledge sources do not provide additional documented workarounds beyond adjusting host permissions and re-running the install.