coollabsio / coolify

An open-source & self-hostable Heroku / Netlify / Vercel alternative.
https://coolify.io
Apache License 2.0
34.32k stars 1.86k forks source link

[Bug]: Supabase is not working. #2938

Closed fabioallexandr3 closed 3 months ago

fabioallexandr3 commented 3 months ago

Description

I am using Supabase, and until yesterday it was working perfectly. However, today I tried to deploy a new instance, and it no longer works.

Minimal Reproduction (if possible, example repository)

https://github.com/user-attachments/assets/90d2ea0c-27da-4125-98d4-cf515c6d0ed5

Exception or Error

Saved configuration files to /data/coolify/services/hwgk4wo. Creating Docker network. Starting service. Pulling images. supabase-edge-functions Pulling supabase-kong Pulling supabase-vector Pulling supabase-meta Pulling realtime-dev Pulling minio-createbucket Pulling supabase-storage Pulling supabase-minio Pulling supabase-analytics Pulling supabase-auth Pulling supabase-rest Pulling supabase-db Pulling supabase-studio Pulling imgproxy Pulling supabase-analytics Pulled supabase-minio Pulled supabase-studio Pulled supabase-vector Pulled supabase-storage Pulled supabase-kong Pulled imgproxy Pulled supabase-rest Pulled supabase-meta Pulled supabase-db Pulled supabase-auth Pulled minio-createbucket Pulled realtime-dev Pulled supabase-edge-functions Pulled Starting containers. Volume "hwgk4wo_supabase-db-data" Creating Volume "hwgk4wo_supabase-db-data" Created Volume "hwgk4wo_supabase-db-config" Creating Volume "hwgk4wo_supabase-db-config" Created Container supabase-vector-hwgk4wo Creating Container imgproxy-hwgk4wo Creating Container supabase-minio-hwgk4wo Creating Container supabase-minio-hwgk4wo Created Container supabase-vector-hwgk4wo Created Container minio-createbucket-hwgk4wo Creating Container supabase-db-hwgk4wo Creating Container imgproxy-hwgk4wo Created Container minio-createbucket-hwgk4wo Created Container supabase-db-hwgk4wo Created Container supabase-analytics-hwgk4wo Creating Container supabase-analytics-hwgk4wo Created Container realtime-dev-hwgk4wo Creating Container supabase-studio-hwgk4wo Creating Container supabase-edge-functions-hwgk4wo Creating Container supabase-rest-hwgk4wo Creating Container supabase-auth-hwgk4wo Creating Container supabase-kong-hwgk4wo Creating Container supabase-meta-hwgk4wo Creating Error response from daemon: invalid mount config for type "bind": stat /data/coolify/services/hwgk4wo/volumes/functions/main/index.ts: not a directory

Version

v4.0.0-beta.318

Cloud?

lolcatswag commented 3 months ago

same for me!

ramyvictor commented 3 months ago

@fabioallexandr3 Try converting empty content storages into a directory. The issue is that they are defined as filed. In your case... this file path needs to be converted to a directory image

itskush commented 3 months ago

@fabioallexandr3 Try converting empty content storages into a directory. The issue is that they are defined as filed. In your case... this file path needs to be converted to a directory image

I tried that and it still doesn't work

Edit: I had to delete resource and redeploy, then change Directory Mount /data/coolify/services/y4c8koc/volumes/functions -> /home/deno/functions from file to directory and now i have this error image

Thanks!

NoCapCbas commented 3 months ago

having the same issue currently forced the cleanup, then implemented all empty storages to a directory mount and was able to deploy

itskush commented 3 months ago

having the same issue currently forced the cleanup, then implemented all empty storages to a directory mount and was able to deploy

Awesome! Yeah had to covert those to directories image then the deploy was successful

fabioallexandr3 commented 3 months ago

tendo o mesmo problema atualmente forçou a limpeza, então implementou todos os armazenamentos vazios em uma montagem de diretório e foi capaz de implantar

Incrível! Sim, tive que convertê-los para diretórios, então a implantação foi bem-sucedida imagem

It worked for me as well. I had to change all the empty "File Mount" to "Convert to Directory" and force the cleanup of the containers.

Sucess!

ATTENTION, NO NEED TO FORCE THE CLEANUP! When this is done, the directories come back to life.