-
Notifications
You must be signed in to change notification settings - Fork 294
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Bug report
Describe the bug
supabase
cli cannot connect to the docker daemon started by colima
To Reproduce
Start docker via colima, run supabase start
:
$ supabase start
Error: Failed to connect to Docker daemon. Is Docker running?
Expected behavior
Supabase should start locally
Screenshots
Sample output from running the commands on my machine:
$ docker ps
Cannot connect to the Docker daemon at unix:///Users/xxx/.colima/docker.sock. Is the docker daemon running?
$ colima start
INFO[0000] using docker runtime
INFO[0000] starting colima
INFO[0000] starting ... context=vm
INFO[0031] provisioning ... context=docker
INFO[0031] starting ... context=docker
INFO[0037] waiting for startup to complete ... context=docker
INFO[0037] done
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ docker run --rm grycap/cowsay
________________________________________
/ He who hoots with owls by night cannot \
\ soar with eagles by day. /
----------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
$ supabase start
Error: Failed to connect to Docker daemon. Is Docker running?
System information
- OS: MacOS 12.1
- Version of supabase-js: 0.16.1
- Version of Node.js: v17.3.1
- Version of Docker: 20.10.12, build e91ed5707e
- Version of Colima:
colima version 0.3.2
git commit: 272db4732b90390232ed9bdba955877f46a50552
runtime: docker
arch: x86_64
client: v20.10.12
server: v20.10.11
Additional context
supabase
, docker
and colima
were installed via brew
.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working