-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
abctl install fails with postgres permissions error #41063
Comments
I'm seeing this as well.
abctl:
Docker (actually using colima too, version 0.7.5):
OS:
Output snippet:
|
We think this could be caused by the latest version of Docker Desktop: docker/for-mac#7415 When I downgraded to docker desktop (for mac) 4.33, that solved this. Alternatively, you can switch to the "grpcfuse" file sharing implementation. edit: that would help @techieshark at least. The original issue was on an older version of abctl and docker. |
Confirming the downgrade to Docker 4.33 worked for me |
I got the same issue on Windows. Downgrade Docker Desktop to 4.33 doesn't work. |
This has been fixed in the latest release of abctl. |
Looks like it hasn't been fixed on Windows. I upgrade abctl to 0.19 version but it doesn't work. |
What happened?
On MacOS, running
abctl localinstall
fails with the error below:2024-07-09 15:09:34.187 UTC [47] FATAL: data directory "/var/lib/postgresql/data/pgdata" has wrong ownership
2024-07-09 15:09:34.187 UTC [47] HINT: The server must be started by the user that owns the data directory.
child process exited with exit code 1
initdb: removing contents of data directory "/var/lib/postgresql/data/pgdata"
running bootstrap script ...
ERROR Failed to install airbyte/airbyte Helm Chart
ERROR Unable to install Airbyte locally
ERROR could not install airbyte chart: could not install helm: pre-upgrade hooks failed: 1 error occurred:
* pod airbyte-abctl-airbyte-bootloader failed
What did you expect to happen?
abctl was supposed to finish installation without errors
Abctl Version
Docker Version
OS Version
The text was updated successfully, but these errors were encountered: