Troubleshooting

Solutions to common issues you might encounter.

Docker Not Running

Symptom: Coding Sandbox shows "Docker not found" or fails to create sandboxes.

Solution: Ensure Docker Desktop is installed and running:

bash

# Check if Docker is running
docker info

# If not running, start Docker Desktop from your Applications

On Linux, make sure the Docker daemon is running: sudo systemctl start docker

Symptom: A sandbox stays in "Starting" state or immediately stops.

Solution: Check the sandbox logs for error details:

bash

# View recent logs
csb logs my-project --tail 50

# Check sandbox status
csb info my-project

Common causes include insufficient disk space, port conflicts, or corrupted container images. Try recreating the sandbox if the issue persists.

Symptom: Tunnel shows "Connecting" but never becomes active.

Solution:

bash

csb tunnel disable my-project
csb tunnel enable my-project

Symptom: Error message "Port already in use" when starting a sandbox.

Solution: Check which process is using the port and either stop it or use a different port:

bash

# Find what's using port 8080
lsof -i :8080

# Create sandbox with a different port
csb create --agent claude --name my-project --port 8081:8080

Symptom: Docker containers consuming too much CPU or memory.

Solution: Monitor resource usage and stop unused sandboxes:

bash

# Check resource usage for all sandboxes
csb list --stats

# Stop sandboxes you're not actively using
csb stop idle-project

Resource limits

You can set resource limits in Docker Desktop settings to cap the total CPU and memory available to containers.

If Coding Sandbox is behaving unexpectedly, you can reset the configuration to defaults:

bash

# Reset configuration (preserves sandboxes)
csb config reset

# Full reset (removes all data)
rm -rf ~/.coding-sandbox

A full reset will remove all sandbox data, snapshots, and settings. This cannot be undone.

If you're still experiencing issues:

MCP Server