Skip to content
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.

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

Studio Container Unhealthy after start #22079

Closed
2 tasks done
dmbr0 opened this issue Mar 18, 2024 · 2 comments
Closed
2 tasks done

Studio Container Unhealthy after start #22079

dmbr0 opened this issue Mar 18, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@dmbr0
Copy link

dmbr0 commented Mar 18, 2024

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

The studio container is in an unhealthy status after started and is inaccessible from localhost:3000

To Reproduce

I follow the self hosted instructions.

Get the code

git clone --depth 1 https://github.com/supabase/supabase

Go to the docker folder

cd supabase/docker

Copy the fake env vars

cp .env.example .env

Pull the latest images

docker compose pull

Start the services (in detached mode)

docker compose up -d

Expected behavior

I expect Studio to be accessible from http://localhost:3000

System information

  • OS: Debian Linux 12
  • Browser chrome
@dmbr0 dmbr0 added the bug Something isn't working label Mar 18, 2024
@encima
Copy link
Member

encima commented Mar 19, 2024

Closing this as it is related to #21616

Please comment if you have tried the steps in previous issues and more information about the occurring issue

@encima encima closed this as completed Mar 19, 2024
@dmbr0
Copy link
Author

dmbr0 commented Mar 19, 2024

I have tried changing that line in the docker-compose file with the suggestion from issue #21616 and the line from PR #21276. The health check still does not pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants