Skip to content

Fix Colima Configuration

⚠️ IMPORTANT: This is a known compatibility issue between Supabase and Colima. Supabase tries to mount the Docker socket path as a directory, which Colima doesn't support.

Recommended Solution: Switch to Docker Desktop (see SWITCH_TO_DOCKER_DESKTOP.md or run ./SWITCH_NOW.sh)

If you must use Colima, try the workarounds below, but they may not work due to this limitation.

Quick Fix Commands

1. Check Colima Status

# Check if Colima is running
colima status

2. Ensure Docker Context is Set to Colima

# Check current Docker context
docker context ls

# Use Colima context (important!)
docker context use colima

# Verify Docker works
docker ps

3. Fix Socket Path Issue (if Supabase still fails)

If you see "error while creating mount source path" error:

# Restart Colima to refresh socket
colima stop
colima start

# Ensure Colima context is active
docker context use colima

# Verify Docker works
docker ps

4. Start Supabase

# Now Supabase should work
supabase start

Advanced Fixes

Fix 1: Restart Colima

If Colima is running but Docker still doesn't work:

# Stop Colima
colima stop

# Start it again
colima start

# Verify
docker ps

Fix 2: Delete and Recreate Colima Instance

If restart doesn't work:

# Stop and delete the default instance
colima stop
colima delete default

# Create a new instance
colima start

# Verify
docker ps

Fix 3: Check Docker Context

If you have both Docker Desktop and Colima:

# List all Docker contexts
docker context ls

# Use Colima context
docker context use colima

# Verify
docker ps

Fix 4: Start Colima with Specific Settings

If default settings don't work:

# Stop current instance
colima stop

# Start with explicit settings
colima start --cpu 4 --memory 8

# Verify
docker ps

Fix 5: Check Colima Logs

If Colima won't start:

# Check Colima logs for errors
colima logs

# Or check specific instance
colima logs default

Complete Reset (Last Resort)

If nothing else works:

# 1. Stop Colima
colima stop

# 2. Delete all Colima instances
colima delete default

# 3. Clean up any remaining files (optional)
rm -rf ~/.colima

# 4. Reinstall Colima (if needed)
brew reinstall colima

# 5. Start fresh
colima start

# 6. Verify
docker ps

Verify Everything Works

After fixing Colima, verify the complete setup:

# 1. Check Colima is running
colima status

# 2. Check Docker works
docker ps

# 3. Start Supabase
supabase start

# 4. Verify Supabase is running
supabase status

Common Issues

Issue: "operation not supported" error

Solution:

colima stop
colima start

Issue: Docker context not set correctly

Solution:

docker context use colima
docker ps

Issue: Colima starts but Docker still fails

Solution:

# Check if Docker Desktop is interfering
docker context ls

# Use Colima context explicitly
docker context use colima

# If Docker Desktop is running, stop it
# Then restart Colima
colima stop
colima start

Alternative: Switch to Docker Desktop

If Colima continues to cause issues:

# 1. Stop Colima
colima stop

# 2. Install Docker Desktop
# Download from: https://www.docker.com/products/docker-desktop

# 3. Start Docker Desktop
open -a Docker

# 4. Wait for Docker to start, then verify
docker ps

# 5. Use default Docker context
docker context use default

# 6. Start Supabase
supabase start