https://supabase.com/ logo
Join Discord
Powered by
I have an error when I try to start supabase with ...
# help
r
I have an error when I try to start supabase with docker compose locally. I followed the guide for Selfhost https://supabase.io/docs/guides/self-hosting), I used 
supabase eject
to create the docker-compose.yml Does anyone have an idea?
Copy code
Creating supabase-mail ... error
Creating supabase-db   ...
Creating supabase-kong ...

Creating supabase-db   ... error
6783a03a7ef845b9c8e357e587e38fa12". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for supabase-db  Cannot create container for service db: Conflict. The container name "/supabase-db" is already in use by container "4e98ca987c72bd9b6466ed5c4ddf86ef12d4aCreating supabase-kong ... error

ERROR: for supabase-kong  Cannot create container for service kong: Conflict. The container name "/supabase-kong" is already in use by container "0a4aac0d7df49eb60e2e842c9a4e14aedb0d1e306aa3ebee295a09eda73b2215". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for mail  Cannot create container for service mail: Conflict. The container name "/supabase-mail" is already in use by container "3a9b049efcfe34d6b24667c1c2f42fa6783a03a7ef845b9c8e357e587e38fa12". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for db  Cannot create container for service db: Conflict. The container name "/supabase-db" is already in use by container "4e98ca987c72bd9b6466ed5c4ddf86ef12d4a549a17842b2979ee0396c456b24". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for kong  Cannot create container for service kong: Conflict. The container name "/supabase-kong" is already in use by container "0a4aac0d7df49eb60e2e842c9a4e14aedb0d1e306aa3ebee295a09eda73b2215". You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.
s
I have an error when I try to start supabase with docker compose locally. I followed the guide for Selfhost https://supabase.io/docs/guides/self-hosting), I used 
supabase eject
to create the docker-compose.yml Does anyone have an idea?
Copy code
Creating supabase-mail ... error
Creating supabase-db   ...
Creating supabase-kong ...

Creating supabase-db   ... error
6783a03a7ef845b9c8e357e587e38fa12". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for supabase-db  Cannot create container for service db: Conflict. The container name "/supabase-db" is already in use by container "4e98ca987c72bd9b6466ed5c4ddf86ef12d4aCreating supabase-kong ... error

ERROR: for supabase-kong  Cannot create container for service kong: Conflict. The container name "/supabase-kong" is already in use by container "0a4aac0d7df49eb60e2e842c9a4e14aedb0d1e306aa3ebee295a09eda73b2215". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for mail  Cannot create container for service mail: Conflict. The container name "/supabase-mail" is already in use by container "3a9b049efcfe34d6b24667c1c2f42fa6783a03a7ef845b9c8e357e587e38fa12". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for db  Cannot create container for service db: Conflict. The container name "/supabase-db" is already in use by container "4e98ca987c72bd9b6466ed5c4ddf86ef12d4a549a17842b2979ee0396c456b24". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for kong  Cannot create container for service kong: Conflict. The container name "/supabase-kong" is already in use by container "0a4aac0d7df49eb60e2e842c9a4e14aedb0d1e306aa3ebee295a09eda73b2215". You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.
Try running:
Copy code
sh
docker rm /supabase-db
docker rm /supabase-kong
docker rm /supabase-mail
And then trying the process again
r
The 
docker-compose up
command ? or 
supabase eject
?
s
The 
docker-compose up
r
Copy code
scala
Creating supabase-kong ... done
Creating supabase-mail ... done
Creating supabase-db   ... done
Creating supabase-auth     ... error
Creating supabase-rest ...
Creating supabase-realtime ...

Creating supabase-rest     ... error
b213182ddad33d491c4c325ff2bfaa9e4". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for supabase-rest  Cannot create container for service rest: Conflict. The container name "/supabase-rest" is already in use by container "7554f44295605385119107728a750ffCreating supabase-realtime ... error

ERROR: for supabase-realtime  Cannot create container for service realtime: Conflict. The container name "/supabase-realtime" is already in use by container "47d5706112cea0a76e2e5f6a8bcde190aad934bf95bbcd949f7136ab23d4ee29". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for auth  Cannot create container for service auth: Conflict. The container name "/supabase-auth" is already in use by container "6f218b2fb26fa7bf3fca7361af83140b213182ddad33d491c4c325ff2bfaa9e4". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for rest  Cannot create container for service rest: Conflict. The container name "/supabase-rest" is already in use by container "7554f44295605385119107728a750ff631f62bdfbb55d8b0b0961feefb788eb5". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for realtime  Cannot create container for service realtime: Conflict. The container name "/supabase-realtime" is already in use by container "47d5706112cea0a76e2e5f6a8bcde190aad934bf95bbcd949f7136ab23d4ee29". You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.
docker rm /supabase-auth ?
s
Yep, and for 
/supabase-rest
and 
/supabase-realtime
too
Along with the other 
docker rm
commands above - run them all at the same time
r
Thank you for your help!
s
No worries. If you're ever looking for more in-depth deployment details for self-hosting, I put together a guide last week: https://dev.to/chronsyn/self-hosting-with-supabase-1aii
r
Thanks, I'll look into it right away
Any updates for the slef-hosted Supabase dashboard?
m
Well there was just recently an update
s
Best place to check is the 
feat/studio
branch
r
I'm getting a 401 error
However I put the same value for the anon key in the url and in the kong config file
JWT_SECRET=your-super-secret-jwt-token-with-at-least-32-characters-long Anon key : eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzdXBhYmFzZSIsImlhdCI6MTYyNzIwODU0MCwiZXhwIjoxOTc0MzYzNzQwLCJhdWQiOiIiLCJzdWIiOiIiLCJyb2xlIjoiYW5vbiJ9.sUHErUOiKZ3nHQIxy-7jND6B80Uzf9G4NtMLmL6HXPQ
Everything looks good, yet when I go to I get an unauthorized error (401)
The database is working correctly
s
If you go to 
http://localhost:8000/auth/v1/settings?apikey=<add your api key>
it should return a page which shows your current auth config
r
Same error
Thank you! Supabase services work when I generate the doker-compose with 
supabase eject
... However, when I clone the 
supabase/supabase
repository, authentication does not work and I get a 401 unauthorized error
However, I need to use the Supabase repository because with 
supabase eject
I don't have the storage-api container
m
Hi Rakox, were you able get everything working
r
Yes everything, except the storage API
m
Hhhmmm
r
I also have a problem with the database, it resets if I restart it
m
I am trying to recall the name, however i recall correctly there is a substiture for storage
Do you perhaps any recommendation to do the build process smoother
Thats a bit hardcore
Im wanting to use supabase for my odoo instances
But does not seem to be working
r
I have exactly the same problem ^^
m
Its started, created the database, however from there the front end just times out
r
I can make everything work if I use my own postgresql database and my own proxy instead of Kong
m
I thought might happen
r
But it's useless for the moment as there is not even a dashboard
m
True, which does suck
But sure in time
However even just to use for the other functionality would be great
r
For the moment I only use the storage API, PostgREST and the realtime API
m
Looking to use the restapi etc..
e
we added support for storage in the self hosting setup in the launch week - https://supabase.io/blog/2021/07/27/storage-beta#using-storage-in-local-development
so storage should work both with the self hosting guide and the supabase cli
m
Hey, everything went well, gong to start my build now
Did you get a chance to go throuygh that link
This is actually pretty aweome though
PreviousNext
Powered by