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.

Sign up for GitHub

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

Jump to bottom

Supabase cli not picking up custom db image #3215

Open

niallam22 opened this issue Feb 26, 2025 · 1 comment

niallam22 commented Feb 26, 2025 •

edited

Loading

Describe the bug
When running Supabase start it only the default containers are initiated

To Reproduce
Steps to reproduce the behavior:

clone supabase repo
build custom db image (I was installing an extension)
reference custom image in the db section of the docker-compose file

supabase start
see error

Expected behavior
My custom container with my extension to be started when using supabase start

Screenshots
If applicable, add screenshots to help explain your problem.

System information

Version of CLI: [2.15.8 ]
Version of Docker: [e.g. v28.0.0]

Contributor

sweatybridge commented Feb 27, 2025

Cli doesn't use the self-hosted compose file. To use a custom db image, you have to tag it locally. For eg

docker tag my-custom-image public.ecr.aws/supabase/postgres:15.8.1.044
rm -rf supabase/.temp
supabase start

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment