Bug report

Describe the bug

Whenever I try to start the CLI, it creates a bunch of processes (like thousands), and then uses up all of my available memory. There is no debug output, and it just seems to keep creating processes

To Reproduce

I'm running the command as sudo (due to docker permissions) so it looks something like this:

sudo supabase start

Expected behavior

I expected it to just start the instance locally

Screenshots

I don't have many applicable screenshots, but here is one from my terminal of what happened when I tried to killall the process (focus on the number of processes, not that they couldn't be closed - I forgot to use sudo at first). There were tons more of them too

System information

• OS: Linux
• Version of supabase-cli: 0.3.8
• Version of Node.js: 14.16.1

Additional Information

I am pretty confident that this isn't a docker issue. If I eject the project with supabase eject, then I'm able to run that normally with sudo docker-compose up. However, this isn't ideal, and I'd prefer to use the CLI for running it locally