Why Docker is hard
Docker on macOS runs in a VM, adding a layer of complexity beyond Linux Docker. Container networking, volume mounting, resource limits, and Docker Compose orchestration create confusing failure modes. Error messages reference Linux paths that don't map to macOS. 'Cannot connect to the Docker daemon' can mean a dozen different things.
How Tutor mode helps
Tutor mode sees your Terminal running Docker commands. When a container fails to start, Lumini reads the error output, sees your Dockerfile or compose file, and explains what's wrong. 'This container can't reach localhost:5432 because Docker Desktop on Mac doesn't use host networking — use host.docker.internal instead.'
How Lumini automates tasks
Lumini can run Docker commands for you with approval. 'Lumini, run docker compose up.' 'Lumini, show me running containers.' 'Lumini, run docker logs on the failing container.' 'Lumini, search the web for this Docker error.' Docker commands are subject to the same safety rules as all shell commands.