It was supposed to be simple. I've worked with Supabase before. I've used the Supabase CLI before. This shouldn't take long.
npx supabase start
The Docker images are downloaded successfully and the containers are being built when:
failed to start docker container: Error response from daemon: mounts denied:
The path /socket_mnt/home/username/.docker/desktop/docker.sock is > not shared from the host and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing.
Ummm, what?
The Supabase CLI doesn't place the Docker files into one's repo - it's meant to be transparent. That's great until one runs into problems.
I found a Supabase CLI issue on GitHub that discusses the problem. The problem seems to only occur when using Analytics. The easiest workaround is to update the config.toml
for one's project from:
[analytics]
enabled = false
...
to:
[analytics]
enabled = true
No, I don't like this solution...but it is the easiest (assuming you don't need analytics).
Top comments (0)