Hyperbutler runs Docker on Windows without WSL, reporting 319 MiB at idle
The early Windows 11 project uses Host Compute Service and publishes the missing release checks beside its measurements.
Docker on Windows can have a smaller roommate. Hyperbutler boots a Linux virtual machine directly through Windows Host Compute Service and runs dockerd inside it. The stock Docker command line and Compose connect to that engine. WSL can stay off; Linux still comes to dinner.
The project’s README reports 319 MiB at idle, including its broker service, on a Windows 11 Home laptop with a Core Ultra 7 155H and 32 GB of RAM. That is the developer’s measurement. The same comparison used one engine at a time and default settings. The README’s useful reality check is short: “One machine is not a general result.”
That caveat needs to travel with the number. A person whose containers spend their day compiling a large project has a different workload from an idle engine. Memory saved while doing nothing can be valuable, particularly on a cramped laptop, but it cannot tell you how much a particular build will consume while doing something expensive. The buffet bill comes after the guests arrive.
Hyperbutler splits the work between an engine running as the user, a privileged broker service and an Alpine Linux guest. The broker starts and stops the VM through HCS. The user-side engine handles API traffic, networking and shared files. Daily operation can therefore run without repeatedly asking for administrator rights, after installation sets up the service.
The sparse data disk is designed to return freed space to Windows. That is another claim worth measuring on your own image churn, since deleting containers should not require a second hobby in virtual-disk housekeeping. The developer also reports bind-mount measurements, but these remain the same single-laptop comparison rather than a universal speed ranking.
Several familiar Docker Desktop features are outside this project’s scope. The README names Kubernetes, Windows containers and extensions among Desktop’s advantages. Hyperbutler targets Linux containers on x64 Windows 11. A Windows 10 machine or a team depending on Windows containers cannot be rescued by squinting harder at the memory row.
The release status is unusually useful reading. The first version passed the developer’s 24-hour command soak, but a clean-PC installation and a real sleep test were among the checks still unrun when the README was read. Builds were also not code-signed. Those limits argue for a trial machine and a real suspend-and-resume cycle before a team depends on it. No amount of idle thrift makes a sleeping laptop wake politely by implication.
An evaluation could start with one disposable Compose project: verify mounts, file-change notifications, published ports and restart behavior, then repeat its actual build. The broader possibility is a more replaceable Windows container layer that lets familiar clients survive an engine change. Whether that feels uneventful after a week of real laptop use remains the test. Containers have enough moving parts without the furniture moving too.
The butler still needs a trial shift.