github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-03-12 10:05:25 -05:00
Code Issues 155 Packages Projects Releases Wiki Activity

Supabase template fails running #9

New Issue
Closed
opened 2025-11-22 20:29:05 -06:00 by GiteaMirror · 25 comments
GiteaMirror commented 2025-11-22 20:29:05 -06:00
Owner
Copy Link

Originally created by @TheMikeyRoss on GitHub (Mar 12, 2025).

To Reproduce

  1. Create a project
  2. create a template service
  3. choose supabase
  4. see the error mentioned below

Current vs. Expected behavior

it should pull all the images and run normally, instead im getting this in the logs:

Initializing deployment
Creating File 'docker-compose.yml' to /etc/dokploy/compose/dd-supabase-9qcbed/code: ✅
File 'docker-compose.yml' created: ✅
╔══════════════════════════════════════════════════════════════════════════════╗
║                                                                              ║
║ App Name: dd-supabase-9qcbed                                                 ║
║ Build Compose 🐳                                                             ║
║ Detected: 1 mounts 📂                                                        ║
║ Command: docker compose -p dd-supabase-9qcbed -f docker-compose.yml up -d    ║
║ --build --remove-orphans                                                     ║
║ Source Type: docker raw ✅                                                   ║
║ Compose Type: docker-compose ✅                                              ║
║                                                                              ║
╚══════════════════════════════════════════════════════════════════════════════╝
time="2025-03-12T06:52:05Z" level=warning msg="/etc/dokploy/compose/dd-supabase-9qcbed/code/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
Volume "dd-supabase-9qcbed_db-config-dd-supabase-9qcbed"  Creating
Volume "dd-supabase-9qcbed_db-config-dd-supabase-9qcbed"  Created
Container supabase-vector  Creating
Container supabase-imgproxy  Creating
Container supabase-imgproxy  Created
Container supabase-vector  Created
Container supabase-db  Creating
Container supabase-db  Created
Container supabase-analytics  Creating
Container supabase-analytics  Created
Container supabase-kong  Creating
Container supabase-studio  Creating
Container supabase-auth  Creating
Container supabase-edge-functions  Creating
Container realtime-dev.supabase-realtime  Creating
Container supabase-rest  Creating
Container supabase-meta  Creating
Container supabase-studio  Created
Container supabase-kong  Created
Container supabase-rest  Created
Container supabase-storage  Creating
Container supabase-auth  Created
Container supabase-edge-functions  Created
Container realtime-dev.supabase-realtime  Created
Container supabase-meta  Created
Container supabase-storage  Created
Container supabase-imgproxy  Starting
Container supabase-vector  Starting
Container supabase-vector  Started
Container supabase-vector  Waiting
Container supabase-imgproxy  Started
Container supabase-vector  Error
dependency failed to start: container supabase-vector exited (78)
Error ❌ time="2025-03-12T06:52:05Z" level=warning msg="/etc/dokploy/compose/dd-supabase-9qcbed/code/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
Volume "dd-supabase-9qcbed_db-config-dd-supabase-9qcbed"  Creating
Volume "dd-supabase-9qcbed_db-config-dd-supabase-9qcbed"  Created
Container supabase-vector  Creating
Container supabase-imgproxy  Creating
Container supabase-imgproxy  Created
Container supabase-vector  Created
Container supabase-db  Creating
Container supabase-db  Created
Container supabase-analytics  Creating
Container supabase-analytics  Created
Container supabase-kong  Creating
Container supabase-studio  Creating
Container supabase-auth  Creating
Container supabase-edge-functions  Creating
Container realtime-dev.supabase-realtime  Creating
Container supabase-rest  Creating
Container supabase-meta  Creating
Container supabase-studio  Created
Container supabase-kong  Created
Container supabase-rest  Created
Container supabase-storage  Creating
Container supabase-auth  Created
Container supabase-edge-functions  Created
Container realtime-dev.supabase-realtime  Created
Container supabase-meta  Created
Container supabase-storage  Created
Container supabase-imgproxy  Starting
Container supabase-vector  Starting
Container supabase-vector  Started
Container supabase-vector  Waiting
Container supabase-imgproxy  Started
Container supabase-vector  Error
dependency failed to start: container supabase-vector exited (78)

Provide environment information

Ubuntu 24.04
Dokploy 0.20.2

Which area(s) are affected? (Select all that apply)

Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Yes

Originally created by @TheMikeyRoss on GitHub (Mar 12, 2025). ### To Reproduce 1. Create a project 2. create a template service 3. choose supabase 4. see the error mentioned below ### Current vs. Expected behavior it should pull all the images and run normally, instead im getting this in the logs: ``` Initializing deployment Creating File 'docker-compose.yml' to /etc/dokploy/compose/dd-supabase-9qcbed/code: ✅ File 'docker-compose.yml' created: ✅ ╔══════════════════════════════════════════════════════════════════════════════╗ ║ ║ ║ App Name: dd-supabase-9qcbed ║ ║ Build Compose 🐳 ║ ║ Detected: 1 mounts 📂 ║ ║ Command: docker compose -p dd-supabase-9qcbed -f docker-compose.yml up -d ║ ║ --build --remove-orphans ║ ║ Source Type: docker raw ✅ ║ ║ Compose Type: docker-compose ✅ ║ ║ ║ ╚══════════════════════════════════════════════════════════════════════════════╝ time="2025-03-12T06:52:05Z" level=warning msg="/etc/dokploy/compose/dd-supabase-9qcbed/code/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion" Volume "dd-supabase-9qcbed_db-config-dd-supabase-9qcbed" Creating Volume "dd-supabase-9qcbed_db-config-dd-supabase-9qcbed" Created Container supabase-vector Creating Container supabase-imgproxy Creating Container supabase-imgproxy Created Container supabase-vector Created Container supabase-db Creating Container supabase-db Created Container supabase-analytics Creating Container supabase-analytics Created Container supabase-kong Creating Container supabase-studio Creating Container supabase-auth Creating Container supabase-edge-functions Creating Container realtime-dev.supabase-realtime Creating Container supabase-rest Creating Container supabase-meta Creating Container supabase-studio Created Container supabase-kong Created Container supabase-rest Created Container supabase-storage Creating Container supabase-auth Created Container supabase-edge-functions Created Container realtime-dev.supabase-realtime Created Container supabase-meta Created Container supabase-storage Created Container supabase-imgproxy Starting Container supabase-vector Starting Container supabase-vector Started Container supabase-vector Waiting Container supabase-imgproxy Started Container supabase-vector Error dependency failed to start: container supabase-vector exited (78) Error ❌ time="2025-03-12T06:52:05Z" level=warning msg="/etc/dokploy/compose/dd-supabase-9qcbed/code/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion" Volume "dd-supabase-9qcbed_db-config-dd-supabase-9qcbed" Creating Volume "dd-supabase-9qcbed_db-config-dd-supabase-9qcbed" Created Container supabase-vector Creating Container supabase-imgproxy Creating Container supabase-imgproxy Created Container supabase-vector Created Container supabase-db Creating Container supabase-db Created Container supabase-analytics Creating Container supabase-analytics Created Container supabase-kong Creating Container supabase-studio Creating Container supabase-auth Creating Container supabase-edge-functions Creating Container realtime-dev.supabase-realtime Creating Container supabase-rest Creating Container supabase-meta Creating Container supabase-studio Created Container supabase-kong Created Container supabase-rest Created Container supabase-storage Creating Container supabase-auth Created Container supabase-edge-functions Created Container realtime-dev.supabase-realtime Created Container supabase-meta Created Container supabase-storage Created Container supabase-imgproxy Starting Container supabase-vector Starting Container supabase-vector Started Container supabase-vector Waiting Container supabase-imgproxy Started Container supabase-vector Error dependency failed to start: container supabase-vector exited (78) ``` ### Provide environment information ```bash Ubuntu 24.04 Dokploy 0.20.2 ``` ### Which area(s) are affected? (Select all that apply) Docker Compose ### Are you deploying the applications where Dokploy is installed or on a remote server? Same server where Dokploy is installed ### Additional context _No response_ ### Will you send a PR to fix it? Yes
GiteaMirror commented 2025-11-22 20:29:06 -06:00
Author
Owner
Copy Link

@DCodeProg commented on GitHub (Mar 12, 2025):

I have the same issue since v0.20.0. The vector container logs are :

2025-03-12T12:37:51.910Z 2025-03-12T12:37:51.907532Z  INFO vector::app: Internal log rate limit configured. internal_log_rate_secs=10
2025-03-12T12:37:51.912Z 2025-03-12T12:37:51.912847Z  INFO vector::app: Log level is enabled. level="vector=info,codec=info,vrl=info,file_source=info,tower_limit=trace,rdkafka=info,buffers=info,lapin=info,kube=info"
2025-03-12T12:37:51.917Z 2025-03-12T12:37:51.917052Z  INFO vector::app: Loading configs. paths=["etc/vector/vector.yml"]
2025-03-12T12:37:51.918Z 2025-03-12T12:37:51.918496Z ERROR vector::cli: Configuration error. error=Is a directory (os error 21)
@DCodeProg commented on GitHub (Mar 12, 2025): I have the same issue since v0.20.0. The vector container logs are : ``` 2025-03-12T12:37:51.910Z 2025-03-12T12:37:51.907532Z INFO vector::app: Internal log rate limit configured. internal_log_rate_secs=10 2025-03-12T12:37:51.912Z 2025-03-12T12:37:51.912847Z INFO vector::app: Log level is enabled. level="vector=info,codec=info,vrl=info,file_source=info,tower_limit=trace,rdkafka=info,buffers=info,lapin=info,kube=info" 2025-03-12T12:37:51.917Z 2025-03-12T12:37:51.917052Z INFO vector::app: Loading configs. paths=["etc/vector/vector.yml"] 2025-03-12T12:37:51.918Z 2025-03-12T12:37:51.918496Z ERROR vector::cli: Configuration error. error=Is a directory (os error 21) ```
GiteaMirror commented 2025-11-22 20:29:06 -06:00
Author
Owner
Copy Link

@DCodeProg commented on GitHub (Mar 12, 2025):

It seems to be an issue with the template volumes setup

@DCodeProg commented on GitHub (Mar 12, 2025): It seems to be an issue with the template volumes setup
GiteaMirror commented 2025-11-22 20:29:06 -06:00
Author
Owner
Copy Link

@merlionme commented on GitHub (Mar 12, 2025):

Can confirm the same error is occurring

Ubuntu 24.04
Dokploy 0.20.2

Initializing deployment
╔══════════════════════════════════════════════════════════════════════════════╗
║                                                                              ║
║ App Name: test-supabase-svpmyf                                               ║
║ Build Compose 🐳                                                             ║
║ Detected: 1 mounts 📂                                                        ║
║ Command: docker compose -p test-supabase-svpmyf -f docker-compose.yml up -d  ║
║ --build --remove-orphans                                                     ║
║ Source Type: docker raw ✅                                                   ║
║ Compose Type: docker-compose ✅                                              ║
║                                                                              ║
╚══════════════════════════════════════════════════════════════════════════════╝
time="2025-03-12T14:05:06Z" level=warning msg="/etc/dokploy/compose/test-supabase-svpmyf/code/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
Volume "test-supabase-svpmyf_db-config-test-supabase-svpmyf-test-supabase-svpmyf"  Creating
Volume "test-supabase-svpmyf_db-config-test-supabase-svpmyf-test-supabase-svpmyf"  Created
Container supabase-vector  Created
Container supabase-imgproxy  Created
Container supabase-meta  Stopping
Container supabase-storage  Stopping
Container realtime-dev.supabase-realtime  Stopping
Container supabase-auth  Stopping
Container realtime-dev.supabase-realtime  Stopped
Container supabase-storage  Stopped
Container supabase-rest  Stopping
Container supabase-auth  Stopped
Container supabase-meta  Stopped
Container supabase-rest  Stopped
Container supabase-analytics  Stopping
Container supabase-analytics  Stopped
Container supabase-db  Recreate
Container supabase-db  Recreated
Container supabase-analytics  Created
Container supabase-meta  Created
Container supabase-rest  Created
Container supabase-storage  Created
Container supabase-auth  Created
Container realtime-dev.supabase-realtime  Created
Container supabase-vector  Starting
Container supabase-imgproxy  Starting
Container supabase-vector  Started
Container supabase-vector  Waiting
Container supabase-imgproxy  Started
Container supabase-vector  Error
dependency failed to start: container supabase-vector exited (78)
Error ❌ time="2025-03-12T14:05:06Z" level=warning msg="/etc/dokploy/compose/test-supabase-svpmyf/code/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
Volume "test-supabase-svpmyf_db-config-test-supabase-svpmyf-test-supabase-svpmyf"  Creating
Volume "test-supabase-svpmyf_db-config-test-supabase-svpmyf-test-supabase-svpmyf"  Created
Container supabase-vector  Created
Container supabase-imgproxy  Created
Container supabase-meta  Stopping
Container supabase-storage  Stopping
Container realtime-dev.supabase-realtime  Stopping
Container supabase-auth  Stopping
Container realtime-dev.supabase-realtime  Stopped
Container supabase-storage  Stopped
Container supabase-rest  Stopping
Container supabase-auth  Stopped
Container supabase-meta  Stopped
Container supabase-rest  Stopped
Container supabase-analytics  Stopping
Container supabase-analytics  Stopped
Container supabase-db  Recreate
Container supabase-db  Recreated
Container supabase-analytics  Created
Container supabase-meta  Created
Container supabase-rest  Created
Container supabase-storage  Created
Container supabase-auth  Created
Container realtime-dev.supabase-realtime  Created
Container supabase-vector  Starting
Container supabase-imgproxy  Starting
Container supabase-vector  Started
Container supabase-vector  Waiting
Container supabase-imgproxy  Started
Container supabase-vector  Error
dependency failed to start: container supabase-vector exited (78)
@merlionme commented on GitHub (Mar 12, 2025): Can confirm the same error is occurring Ubuntu 24.04 Dokploy 0.20.2 --- ``` Initializing deployment ╔══════════════════════════════════════════════════════════════════════════════╗ ║ ║ ║ App Name: test-supabase-svpmyf ║ ║ Build Compose 🐳 ║ ║ Detected: 1 mounts 📂 ║ ║ Command: docker compose -p test-supabase-svpmyf -f docker-compose.yml up -d ║ ║ --build --remove-orphans ║ ║ Source Type: docker raw ✅ ║ ║ Compose Type: docker-compose ✅ ║ ║ ║ ╚══════════════════════════════════════════════════════════════════════════════╝ time="2025-03-12T14:05:06Z" level=warning msg="/etc/dokploy/compose/test-supabase-svpmyf/code/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion" Volume "test-supabase-svpmyf_db-config-test-supabase-svpmyf-test-supabase-svpmyf" Creating Volume "test-supabase-svpmyf_db-config-test-supabase-svpmyf-test-supabase-svpmyf" Created Container supabase-vector Created Container supabase-imgproxy Created Container supabase-meta Stopping Container supabase-storage Stopping Container realtime-dev.supabase-realtime Stopping Container supabase-auth Stopping Container realtime-dev.supabase-realtime Stopped Container supabase-storage Stopped Container supabase-rest Stopping Container supabase-auth Stopped Container supabase-meta Stopped Container supabase-rest Stopped Container supabase-analytics Stopping Container supabase-analytics Stopped Container supabase-db Recreate Container supabase-db Recreated Container supabase-analytics Created Container supabase-meta Created Container supabase-rest Created Container supabase-storage Created Container supabase-auth Created Container realtime-dev.supabase-realtime Created Container supabase-vector Starting Container supabase-imgproxy Starting Container supabase-vector Started Container supabase-vector Waiting Container supabase-imgproxy Started Container supabase-vector Error dependency failed to start: container supabase-vector exited (78) Error ❌ time="2025-03-12T14:05:06Z" level=warning msg="/etc/dokploy/compose/test-supabase-svpmyf/code/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion" Volume "test-supabase-svpmyf_db-config-test-supabase-svpmyf-test-supabase-svpmyf" Creating Volume "test-supabase-svpmyf_db-config-test-supabase-svpmyf-test-supabase-svpmyf" Created Container supabase-vector Created Container supabase-imgproxy Created Container supabase-meta Stopping Container supabase-storage Stopping Container realtime-dev.supabase-realtime Stopping Container supabase-auth Stopping Container realtime-dev.supabase-realtime Stopped Container supabase-storage Stopped Container supabase-rest Stopping Container supabase-auth Stopped Container supabase-meta Stopped Container supabase-rest Stopped Container supabase-analytics Stopping Container supabase-analytics Stopped Container supabase-db Recreate Container supabase-db Recreated Container supabase-analytics Created Container supabase-meta Created Container supabase-rest Created Container supabase-storage Created Container supabase-auth Created Container realtime-dev.supabase-realtime Created Container supabase-vector Starting Container supabase-imgproxy Starting Container supabase-vector Started Container supabase-vector Waiting Container supabase-imgproxy Started Container supabase-vector Error dependency failed to start: container supabase-vector exited (78) ```
GiteaMirror commented 2025-11-22 20:29:06 -06:00
Author
Owner
Copy Link

@Siumauricio commented on GitHub (Mar 13, 2025):

Templates are being managed in https://github.com/Dokploy/templates, so we can move this issue for now

@Siumauricio commented on GitHub (Mar 13, 2025): Templates are being managed in https://github.com/Dokploy/templates, so we can move this issue for now
GiteaMirror commented 2025-11-22 20:29:06 -06:00
Author
Owner
Copy Link

@DCodeProg commented on GitHub (Mar 14, 2025):

Templates are being managed in https://github.com/Dokploy/templates, so we can move this issue for now

@Siumauricio But it seams to be more an issue with volume mounting than an issue with the supabase template

@DCodeProg commented on GitHub (Mar 14, 2025): > Templates are being managed in https://github.com/Dokploy/templates, so we can move this issue for now @Siumauricio But it seams to be more an issue with volume mounting than an issue with the supabase template
GiteaMirror commented 2025-11-22 20:29:06 -06:00
Author
Owner
Copy Link

@hkdahal commented on GitHub (Mar 14, 2025):

Seems like the version in the template is the issue with the docker. I removed it, and it got past that error but I am getting "dependency failed to start" error, but version error went away.

Reference: https://forums.docker.com/t/docker-compose-yml-version-is-obsolete/141313/2

@hkdahal commented on GitHub (Mar 14, 2025): Seems like the version in the template is the issue with the docker. I removed it, and it got past that error but I am getting "dependency failed to start" error, but version error went away. Reference: https://forums.docker.com/t/docker-compose-yml-version-is-obsolete/141313/2
GiteaMirror commented 2025-11-22 20:29:07 -06:00
Author
Owner
Copy Link

@Lkhagvadelger commented on GitHub (Mar 15, 2025):

I am having same error.
But 7 days ago I installed Supabase on Coolify using Coolify template and its working as expected.

Today I tried to use on Dokploy on another Ubuntu server and tried to install Supabase using Dokploy template. But getting this error and cant go further.

@Lkhagvadelger commented on GitHub (Mar 15, 2025): I am having same error. But 7 days ago I installed Supabase on Coolify using Coolify template and its working as expected. Today I tried to use on Dokploy on another Ubuntu server and tried to install Supabase using Dokploy template. But getting this error and cant go further.
GiteaMirror commented 2025-11-22 20:29:07 -06:00
Author
Owner
Copy Link

@CarlosBranty commented on GitHub (Mar 15, 2025):

some one got any solution :D?

@CarlosBranty commented on GitHub (Mar 15, 2025): some one got any solution :D?
GiteaMirror commented 2025-11-22 20:29:07 -06:00
Author
Owner
Copy Link

@Siumauricio commented on GitHub (Mar 15, 2025):

Issue is already fixed @CarlosBranty

@Siumauricio commented on GitHub (Mar 15, 2025): Issue is already fixed @CarlosBranty
GiteaMirror commented 2025-11-22 20:29:07 -06:00
Author
Owner
Copy Link

@Lkhagvadelger commented on GitHub (Mar 16, 2025):

I am new with Dokploy. How can i get this update on my current installed version of Dokploy?

@Lkhagvadelger commented on GitHub (Mar 16, 2025): I am new with Dokploy. How can i get this update on my current installed version of Dokploy?
GiteaMirror commented 2025-11-22 20:29:08 -06:00
Author
Owner
Copy Link

@Siumauricio commented on GitHub (Mar 16, 2025):

@Lkhagvadelger Just create a new supabase application and that should work

@Siumauricio commented on GitHub (Mar 16, 2025): @Lkhagvadelger Just create a new supabase application and that should work
GiteaMirror commented 2025-11-22 20:29:08 -06:00
Author
Owner
Copy Link

@arladmin commented on GitHub (Mar 16, 2025):

@Siumauricio
Sorry, but did you try creating & deploying one (just Create > no modifications > Deploy), since the update?

PS: there appear to be several pending issues (WARN, ERROR), in the logs of each of the containers, and the main page not being accessible at all:

Image

supabase-db:

Image

supabase-kong:

Image

@arladmin commented on GitHub (Mar 16, 2025): @Siumauricio Sorry, but did you try creating & deploying one (just Create > no modifications > Deploy), since the update? PS: there appear to be several pending issues (`WARN`, `ERROR`), in the logs of each of the containers, and the main page not being accessible at all: --- ![Image](https://github.com/user-attachments/assets/658d86cc-cc6c-48dc-98fb-9cbdfe2136d9) --- `supabase-db`: ![Image](https://github.com/user-attachments/assets/ed7cc0fb-0079-450c-b982-1b7d21666baf) --- `supabase-kong`: ![Image](https://github.com/user-attachments/assets/9a03bb94-3267-43fd-87b6-8a3a675b0c59) ---
GiteaMirror commented 2025-11-22 20:29:08 -06:00
Author
Owner
Copy Link

@Siumauricio commented on GitHub (Mar 16, 2025):

Yes, I created a clean supabase template and is working for me

Image

Image

@Siumauricio commented on GitHub (Mar 16, 2025): Yes, I created a clean supabase template and is working for me ![Image](https://github.com/user-attachments/assets/d5e3b4a8-96e2-4482-8e2e-b1cacb8f47e0) ![Image](https://github.com/user-attachments/assets/dfa0646a-b683-4423-a204-e35960889b98)
GiteaMirror commented 2025-11-22 20:29:08 -06:00
Author
Owner
Copy Link

@arladmin commented on GitHub (Mar 16, 2025):

Yes, I created a clean supabase template and is working for me

Image

Image

@Siumauricio These logs are the same in my case as well.

Yet, the above issues also persist.

@arladmin commented on GitHub (Mar 16, 2025): > Yes, I created a clean supabase template and is working for me > > ![Image](https://github.com/user-attachments/assets/d5e3b4a8-96e2-4482-8e2e-b1cacb8f47e0) > > ![Image](https://github.com/user-attachments/assets/dfa0646a-b683-4423-a204-e35960889b98) @Siumauricio These logs are the same in my case as well. Yet, the above issues also persist.
GiteaMirror commented 2025-11-22 20:29:08 -06:00
Author
Owner
Copy Link

@Siumauricio commented on GitHub (Mar 16, 2025):

Can you show the domains @arladmin ?

@Siumauricio commented on GitHub (Mar 16, 2025): Can you show the domains @arladmin ?
GiteaMirror commented 2025-11-22 20:29:08 -06:00
Author
Owner
Copy Link

@arladmin commented on GitHub (Mar 16, 2025):

Can you show the domains @arladmin ?

@Siumauricio

There's just one automatically deployed domain:

IMG_20250316_134036.jpg

@arladmin commented on GitHub (Mar 16, 2025): > Can you show the domains @arladmin ? @Siumauricio There's just one automatically deployed domain: ![IMG_20250316_134036.jpg](https://github.com/user-attachments/assets/a286289b-147e-42cf-a71d-dd8f0989dcbb)
GiteaMirror commented 2025-11-22 20:29:09 -06:00
Author
Owner
Copy Link

@arladmin commented on GitHub (Mar 27, 2025):

@Siumauricio Is there no fix for this issue?

@arladmin commented on GitHub (Mar 27, 2025): @Siumauricio Is there no fix for this issue?
GiteaMirror commented 2025-11-22 20:29:09 -06:00
Author
Owner
Copy Link

@DCodeProg commented on GitHub (Mar 27, 2025):

@Siumauricio Is there no fix for this issue?

This issue seams to be fixed. It work for me

@DCodeProg commented on GitHub (Mar 27, 2025): > [@Siumauricio](https://github.com/Siumauricio) Is there no fix for this issue? This issue seams to be fixed. It work for me
GiteaMirror commented 2025-11-22 20:29:09 -06:00
Author
Owner
Copy Link

@arladmin commented on GitHub (Mar 27, 2025):

@DCodeProg
Well, any recommendation on how to diagnose the root cause?

@arladmin commented on GitHub (Mar 27, 2025): @DCodeProg Well, any recommendation on how to diagnose the root cause?
GiteaMirror commented 2025-11-22 20:29:09 -06:00
Author
Owner
Copy Link

@sirtrade commented on GitHub (Apr 25, 2025):

Have same problem. Any solution?

@sirtrade commented on GitHub (Apr 25, 2025): Have same problem. Any solution?
GiteaMirror commented 2025-11-22 20:29:10 -06:00
Author
Owner
Copy Link

@fdciabdul commented on GitHub (Jun 5, 2025):

have problem with storage

@fdciabdul commented on GitHub (Jun 5, 2025): have problem with storage
GiteaMirror commented 2025-11-22 20:29:10 -06:00
Author
Owner
Copy Link

@cammurray commented on GitHub (Jun 15, 2025):

Same issue with a brand new supabase as per the documentation. This issue isn't fixed.

@cammurray commented on GitHub (Jun 15, 2025): Same issue with a brand new supabase as per the documentation. This issue isn't fixed.
GiteaMirror commented 2025-11-22 20:29:10 -06:00
Author
Owner
Copy Link

@sebasegura97 commented on GitHub (Jul 7, 2025):

Same issue with a fresh new install of supabase in dokploy, the service is not accesible

@sebasegura97 commented on GitHub (Jul 7, 2025): Same issue with a fresh new install of supabase in dokploy, the service is not accesible
GiteaMirror commented 2025-11-22 20:29:10 -06:00
Author
Owner
Copy Link

@fdciabdul commented on GitHub (Jul 9, 2025):

the solution is just fork the supabase repo, and run the compose .. the template from dokploy is not working

@fdciabdul commented on GitHub (Jul 9, 2025): the solution is just fork the supabase repo, and run the compose .. the template from dokploy is not working
GiteaMirror commented 2025-11-22 20:29:10 -06:00
Author
Owner
Copy Link

@samiralavi commented on GitHub (Nov 15, 2025):

I have updated the template for Supabase in this PR: https://github.com/Dokploy/templates/pull/537
Please check. Currently, I am hitting a Docker version incompatibility issue on my VPS.

@samiralavi commented on GitHub (Nov 15, 2025): I have updated the template for Supabase in this PR: https://github.com/Dokploy/templates/pull/537 Please check. Currently, I am hitting a Docker version incompatibility issue on my VPS.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#9
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?