Skip to content

Hawser 0.1.0

Pre-release
Pre-release

Choose a tag to compare

@zcsizmadia zcsizmadia released this 01 Sep 20:12
· 160 commits to main since this release
2fe3b46

The first installable Hawser: the upstream Docker Engine on Windows via WSL2, reached by stock docker.exe over a named pipe. No license fees, no Electron, no Kubernetes.

What works

hawser install     # verified rootfs download -> WSL2 distro -> engine start -> docker context
hawser proxy       # serves the pipe, translates Windows bind paths, coexists with Docker Desktop
docker --context hawser run --rm hello-world
hawser uninstall   # removes everything it created, restores your previous context
  • The real Docker API — compose, bind mounts with Windows paths (-v C:\src:/app), exec, logs -f, and anything that speaks to docker.sock work unmodified
  • Coexists with Docker Desktop: never takes the default pipe if Desktop holds it; both engines usable side by side
  • Deterministic by contract: the engine (dockerd 29.7.2, containerd 2.1.4, runc 1.3.0, buildkit 0.27.0) is pinned in an embedded manifest, checksum-verified before import, and built from upstream source — the SBOM points at commits
  • Verified by a 13-stage acceptance suite on real WSL2, including a compose stack, an interrupted client, and a Docker-Desktop-still-works check

Honest limits

  • Pre-release, unsigned binaries — SmartScreen will warn; verify against SHA256SUMS (signing lands in v0.4)
  • A logged-on session is required (a WSL2 constraint that binds every WSL-based engine; auto-logon covers headless runners)
  • hawser proxy runs in the foreground; the always-on supervisor is v0.2
  • Interrupted clients can leave relay processes alive for up to 5 minutes (bounded; fully fixed by the v0.2 agent)
  • Linux containers only, x64 and arm64 Windows

Install

  1. Download the zip for your architecture below and extract hawser.exe
  2. hawser.exe install
  3. hawser.exe proxy (keep it running)
  4. docker --context hawser run --rm hello-world

Binaries are attached automatically by the release workflow, with SHA256SUMS.