supabase-studio is unhealthy when self-hosting on Ubuntu

[outSH]

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.
  • Similar issue here: https://github.com/orgs/supabase/discussions/21558

Describe the bug

I can't run supabase in docker using any Ubuntu machine (checked multiple environments) because studio is unhealthy. Studio container doesn't contain any helpful information (just that it's listening on port 3000), I can provide debug logs if you let me know how to enable them :)

To Reproduce

1. Follow https://supabase.com/docs/guides/self-hosting/docker on any environment listed in system information below.
2. The supabase-studio is unhealthy

Expected behavior

All containers should be healthy.

System information

• OS:
  • Ubuntu 22.04.3 LTS on WSL2
  • Ubuntu 20.04.6 LTS VM on HyperV
  • Docker in docker (docker:25.0.5-dind) on both machines above.
• Branches: master / v0.24.03. Occurred on older tags as well but I did not keep track of them.

Additional context

It used to work in v0.22.10, but this version can't be used anymore because it's docker compose file references image that is not available anymore. We use supabase in DIND container for testing purposes in Hyperledger Cacti project - https://github.com/hyperledger/cacti/tree/main/tools/docker/supabase-all-in-one.

[garrettcam]

See #20655 (comment)

[outSH]

@garrettcam Thanks, it does solve the issue!

However I'd prefer using the docker-compose in the repo without a change. I think the root cause might be caused by node 17+ binding to ipv6 by default:

  ▲ Next.js 13.5.6
  - Local:        http://54207504f03d:3000 # should be 127.0.0.1 for localhost ping to work
  - Network:      http://172.25.0.8:3000

 ✓ Ready in 293ms

[encima]

Thanks for reporting! Feel free to open a PR to modify the Compose file!