Files

Michael Chus ada15ac777 fix: loading screen via Go handler instead of file:// HTML

- bee-web.service: remove After=bee-audit so Go starts immediately
- Go serves loading page from / when audit JSON not yet present;
  JS polls /api/ready (503 until file exists, 200 when ready)
  then redirects to dashboard
- bee-openbox-session: wait for /healthz (Go binds fast <2s),
  open http://localhost/ directly — no file:// cross-origin issues
- Remove loading.html static file

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-29 10:31:46 +03:00

builder

fix(iso): copy memtest86+ to ISO root via binary hook

2026-03-29 09:02:40 +03:00

overlay

fix: loading screen via Go handler instead of file:// HTML

2026-03-29 10:31:46 +03:00

vendor

Implement audit enrichments, TUI workflows, and production ISO scaffold

2026-03-06 11:56:26 +03:00

README.md

iso: improve burn-in, export, and live boot

2026-03-26 18:56:19 +03:00

README.md

ISO Build

bee ISO is built inside a Debian 12 builder container via iso/builder/build-in-container.sh.

Requirements

Docker Desktop or another Docker-compatible container runtime
Privileged containers enabled
Enough free disk space for builder cache, Debian live-build artifacts, NVIDIA driver cache, and CUDA userspace packages

Build On macOS

From the repository root:

sh iso/builder/build-in-container.sh

The script defaults to linux/amd64 builder containers, so it works on:

Intel Mac
Apple Silicon (M1 / M2 / M3 / M4) via Docker Desktop's Linux VM

You do not need to pass --platform manually for normal ISO builds.

Useful Options

Build with explicit SSH keys baked into the ISO:

sh iso/builder/build-in-container.sh --authorized-keys ~/.ssh/id_ed25519.pub

Rebuild the builder image:

sh iso/builder/build-in-container.sh --rebuild-image

Use a custom cache directory:

sh iso/builder/build-in-container.sh --cache-dir /path/to/cache

Notes

The builder image is automatically rebuilt if the local tag exists for the wrong architecture.
The live ISO boots with Debian live-boot toram, so the read-only medium is copied into RAM during boot and the runtime no longer depends on the original USB/BMC virtual media staying present.
Target systems need enough RAM for the full compressed live medium plus normal runtime overhead, or boot may fail before reaching the TUI.
Override the container platform only if you know why:

BEE_BUILDER_PLATFORM=linux/amd64 sh iso/builder/build-in-container.sh

The shipped ISO is still amd64.
Output ISO artifacts are written under dist/.