Skip to main content
When to pick it — A single machine you own: a laptop to try things, or an on-prem server you run in production. The installer brings up a self-contained Kubernetes cluster (k3d) inside Docker — you don’t need a cluster of your own.

​
Prerequisites

  • A machine: macOS, Linux, or Windows · 2 CPU · 5 GB RAM · 10 GB free disk to run (4 CPU · 16 GB · 50 GB to train on it, with 11–14 GB of memory for Docker).
  • A tracebloc account. The installer signs you in through your browser and registers this machine for you.
That’s it — no Docker or Kubernetes knowledge needed. The installer sets up Docker and the cluster for you.

​
Install

See Quick Start for the full walkthrough, including the inspect-first option.

​
Verify

Your secure environment should also read Online on the clients page.

​
Environment-specific config

Set these as environment variables before the install command (full list in Configuration):
GPUs are auto-detected on Linux (NVIDIA/AMD) — drivers, container toolkit, and device plugin are installed for you.

​
Production notes

  • Local is production-capable. Point it at a server rather than a laptop and it’s a real deployment.
  • Where your datasets live. On macOS and Linux, datasets are stored inside the cluster node by default. They survive stop/start cycles (see Operations) but are wiped when the cluster is deleted, including by tracebloc delete. To keep them on the host instead, install with TB_STORAGE_MODE=hostpath: they then live under the data directory (TRACEBLOC_HOST_DATA_DIR, default ~/.tracebloc; the older HOST_DATA_DIR still works). The Windows installer always stores them on the host.
  • Need more headroom? Re-run the installer on a bigger machine. Extra k3d nodes don’t add capacity: they all share this one machine.
  • For multi-node high availability, use bare-metal or a managed cloud instead.