[Bug]: Supabase initialization error - due to unfinished supabase-db config, supabase-analytics and related services can't start
#4665
Comments
mkpanq
added
🐛 Bug
|
I got the same error on my Coolify Cloud |
|
Not a solution, but a report about a working config. I'm in a test drive with self-hosted coolify on Hetzner (arm64, 2GB RAM), where the target VPS has 8GB RAM (arm64). I assume, as the coolify uses the official self-host docker file, it should work in the same way as the supabase self-host. Anyway, I found this supabase/supabase#30232 , maybe it somehow relates to your issue (and could be related to coolify, too). |
|
I personally had to change this in analytics:
# ...
environment:
# DB_DATABASE: _supabase # change this for ↓
DB_DATABASE: ${POSTGRES_DB} |
|
Unfortunately, the problem is still the same... I'll try to look into @pongraczi proposition later |
|
I tried as @y4my4my4m sugessted. I still get the same error: @y4my4my4m , any suggestion? |
What is in your docker log?
|
|
For newest Coolify version (v4.0.0-beta.380) problem still exists |
|
Here is my log:
|
|
Are you sure, you have enough resurces and the target folders do not exist before?
I just tried again (4th time) this and I am not able to reproduce:
Please note:
|
|
The error didn't appear in my logs: "Database directory appears to contain a database; Skipping initialization" My logs with v4.0.0-beta.380 (Coolify Cloud) |
I referred to the original post. :)
You must be cursed or I am the chosen one. Check below, why. Test case 1, steps:
Test case 2, steps:
In both cases, I just chose the supabase provided by coolify itself, I did not use any docker file from supabase directly. Sorry, I am not able to reproduce the problem even on vps identical to yours, but I hope I gave you some reference (test cases).
|
|
try using centos system deploy supabase |
|
I just upgraded to version v4.0.0-beta.380, some time over the last few versions they changed the file permissions of the I checked another version I have running and they're all For full clarity, I'm not having the permission issue as described above, but a permission issue on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Error Message and Logs
I'm adding fresh, out of the box Supabase service using Coolify menu. After initial creation, I'm not changing anything and just click "Deploy":
Everything is going OK, until
supabase-dbservice creation - there is an error during service initialization - service started, but not every init script was properly run.supabase-dblogs:Because of this,
supabase-analyticscan't properly start:supabase-analyticslogs:Eventually,
supabase-dbservice is displayed as healthy (because service is running properly), but due to unfinished configuration,supabase-analytics(and the rest of the related services, marked depended in compose file) can't start:Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta.379
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04.1 LTS (Noble Numbat)
Additional Information
No response
The text was updated successfully, but these errors were encountered: