-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Supabase gen types --db-url Fails Without Docker Desktop #2536
Comments
Are you generating types for local database or a remote project? It seems like local from your comment but starting a local database relies on docker anyway so I'm confused why you can't use docker for type generation. If you are generating for a remote project, you can use |
I am using the cli for https://github.com/supabase/postgrest-js, which can operate independently of Supabase dependencies. This means it doesn’t require the entire Supabase stack to be installed via Docker. In my setup, the entire environment is placed inside a devcontainer, which is essentially a Docker container without internal Docker support. When a CLI tool depends on Docker, it often results in a substantial download of several gigabytes of various images. This can be quite costly in some locations. It would be greatly appreciated if the CLI could provide an estimate of the data it will download, especially for one-time executions. |
That's a good idea. What I will probably do is to add series of prompts when running tracked here #2551 |
Runneing the following command
npx supabase gen types --lang=typescript --db-url postgresql://postgres:pass@localhost/webstudio
produces the error message:
Docker Desktop is a prerequisite for local development. Follow the official docs to install: https://docs.docker.com/desktop
To Reproduce
npx supabase gen types --lang=typescript --db-url postgresql://postgres:pass@localhost/webstudio
Expected behavior
I am not using any Supabase services to generate types. Installing Docker for type generation seems unnecessary.
The text was updated successfully, but these errors were encountered: