Supabase start hangs without sudo on Ubuntu

[taylorkangbeck]

Describe the bug
For some reason, supabase start just hangs on my Ubuntu machine. Even with the --debug flag there's no useful info. However, things work as expected with a sudo supabase start.

I've tried reinstalling the CLI in 3 ways with the same problem: brew, npm, and deb

To Reproduce
Steps to reproduce the behavior:

1. supabase start

Expected behavior
supabase start works without sudo, or exits with an error message requesting sudo usage.

System information
Rerun the failing command with --create-ticket flag.

• Ticket ID: (can't create ticket because command doesn't exit)
• Version of OS: Ubuntu 22.04
• Version of CLI: 1.178.2
• Version of Docker: 25.0.2
• Versions of services: (supabase services seems to suffer similar issues)

Additional context

• Version of Node.js: 20.6.1

[sweatybridge]

What does docker ps -a say after cli is stuck?

If there are any unhealthy containers, could you also show me ther logs? ie. docker logs <container_name>

You can also try starting docker in rootless mode.

[taylorkangbeck]

It doesn’t get that far, no containers are created. I’m guessing it is unable to communicate with the docker engine at all due to permissions issues?

…

On Sat, Jul 6, 2024 at 8:43 AM, Han Qiao ***@***.***(mailto:On Sat, Jul 6, 2024 at 8:43 AM, Han Qiao <<a href=)> wrote: What does docker ps -a say after cli is stuck? If there are any unhealthy containers, could you also show me ther logs? ie. docker logs <container_name> — Reply to this email directly, [view it on GitHub](#2471 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAR4BRYMCEQAMN3BC7WYXXTZLAGD7AVCNFSM6AAAAABKBA3VLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRHAYDCMRVG4). You are receiving this because you authored the thread.Message ID: ***@***.***>

[sweatybridge]

Yea if it works with sudo, then it's probably a permission issue. Have you enabled docker rootless mode as suggested above? If it still happens, perhaps it's trying to connect to the wrong docker socket.

You can try setting it explicitly with DOCKER_SOCKET=/var/run/docker.sock supabase db start or wherever your rootless docker socket path is.