[Bug]: Supabase deployment/restart fails because minio/mc image cannot be pulled

Description and Error Message

I'm trying to deploy a Supabase instance using the Supabase service/template in Coolify.

The deployment fails while pulling the minio/mc image:

Image minio/mc Pulling
Image supabase/edge-runtime:v1.71.2 Pulling
Image postgrest/postgrest:v14.6 Pulling
Image supabase/supavisor:2.7.4 Pulling
Image supabase/gotrue:v2.186.0 Pulling
Image supabase/logflare:1.31.2 Pulling
Image supabase/storage-api:v1.44.2 Pulling
Image kong/kong:3.9.1 Pulling
Image supabase/realtime:v2.76.5 Pulling
Image darthsim/imgproxy:v3.30.1 Pulling
Image supabase/studio:2026.03.16-sha-5528817 Pulling
Image ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z Pulling
Image supabase/postgres:15.8.1.085 Pulling
Image timberio/vector:0.53.0-alpine Pulling
Image supabase/postgres-meta:v0.95.2 Pulling
Image ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z Pulled
Image kong/kong:3.9.1 Pulled
Image minio/mc Error pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Error response from daemon:
pull access denied for minio/mc, repository does not exist or may require 'docker login':
denied: requested access to the resource is denied

The important part is that this does not only happen during the initial deployment. It also happens when restarting an already running Supabase instance. This means that a production Supabase instance that was previously working can become unavailable simply after performing a restart, because Coolify attempts to pull minio/mc again and the pull fails.

Coolify version

I am currently not running the latest Coolify version.

I am aware that the recommended troubleshooting step is to update to the latest version. However, I am intentionally staying on my current version for the moment because the latest release has introduced other issues that make it unsuitable for my production environment.

That said, I would be surprised if this particular issue were version-specific, because the generated Supabase configuration explicitly references:

minio/mc

while the rest of the MinIO setup uses:

ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z

I would therefore appreciate confirmation whether the Supabase service template has changed in a newer Coolify version, specifically regarding the minio/mc image.

Expected Behavior

Restarting an existing Supabase service should not fail because of an invalid/unavailable auxiliary image.

The Supabase service template should reference a valid and supported minio/mc image/tag, or Coolify should otherwise handle this image without making the entire Supabase stack unavailable.

Actual behavior

Coolify attempts to pull:

minio/mc

and Docker returns:

pull access denied for minio/mc, repository does not exist or may require 'docker login'

This aborts the operation for the entire Supabase stack.

Steps to Reproduce

Create a new Supabase service in Coolify using the built-in Supabase service template. Configure the required environment variables. Start/deploy the service. During the image pull phase, Coolify attempts to pull the minio/mc image. The image pull fails with: Image minio/mc Error pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

Error response from daemon: pull access denied for minio/mc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied The Supabase service fails to start because the required images cannot be pulled.

Additional reproduction case

The same issue also occurs when restarting an already deployed/running Supabase instance:

Have an existing Supabase service deployed through the Coolify Supabase template. Restart the service. Coolify attempts to pull minio/mc again. The same pull access denied error occurs. The Supabase service fails to restart.

Therefore, the issue affects both fresh deployments and restarts of existing instances.

Example Repository URL

No response

Coolify Version

v4.1.2

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.4 LTS

Screenshots / Visuals

Additional Information

Could you please verify whether the current Supabase service template references an outdated/incorrect minio/mc image?

If this has already been fixed in a newer Coolify release, could you also point me to the relevant change/commit so I can determine whether it is possible to apply the fix manually to my current installation?

This is currently causing a production-impacting problem because restarting an otherwise healthy Supabase instance can make the entire service unavailable.