Docker, isolation, and why FLY8HT asks for it

FLY8HT runs a project’s own code on your computer to build and start it. Docker is what lets it do that with real isolation, rather than running directly against your own system.

With Docker

A build runs inside its own disposable container: its own filesystem, its own process space, cleaned up automatically when it’s done. A project you build can’t reach outside that container into the rest of your computer.

Without Docker

FLY8HT falls back to a real local process instead. It is confined to the project’s own workspace folder, but genuinely running with your own user permissions, not inside a separate sandbox. Settings → Security always shows you honestly which mode is actually active, and Settings → Builds lets you force Automatic, Local, or Docker (Docker is only selectable once FLY8HT actually detects it running).

This is a real, disclosed trade-off, not a broken feature. Local execution is completely usable for projects you trust; it just doesn’t provide the same isolation guarantee as a real container.

Installing Docker

FLY8HT never installs anything on your behalf. If a build tells you Docker is required, click through to Docker Desktop’s own official download page, install it normally, and retry the build once it’s running.