Skip to main content
JUMP TO:Quick StartCLI CommandsConfigurationPlaywright APIMCP ServerGitHub Actions
Deployment & Sandboxing / Cross-OS rendering(35 of 37)

Cross-OS rendering

NOT VALIDATED. The renderer is currently repository-source-only: no public image or cross-host byte-equivalence result is published.

Because macOS CoreText and Linux FreeType rasterize fonts differently, teams comparing baselines across macOS laptops and Linux CI runners can build the local linux/amd64 Docker renderer from source.

Deterministic Rendering and Anti-Flake Engine
FIG 01 · DETERMINISTIC STABILIZATION GATES — CLOCK FREEZE · PRNG SEED · NETWORK GUARD · FRAME CONVERGENCE · PII REDACTION

Current status

From a clean clone, run the complete preparation sequence below at the repository root. The Dockerfile requires the renamed npm pack tarball in its build context.

Local build

terminal
$ npm ci
$ npm run build --workspace=packages/cli
$ npm pack ./packages/cli --pack-destination packages/cli/docker
$ mv packages/cli/docker/frontguard-cli-*.tgz packages/cli/docker/frontguard-cli.tgz
$ docker build --platform linux/amd64 -t frontguard/render:0.2.3 packages/cli/docker
$ docker image inspect frontguard/render:0.2.3

Running with --docker

After the image is built, invoke it from a configured project. A container cannot reach a host app through localhost, so this staging example overrides baseUrl deliberately.

configured project terminal
$ npx -p @frontguard/cli frontguard run --docker --url https://staging.example.com

Limit

Use docker manifest inspect only for an image reference you expect to be remote. The current renderer is not yet published, so build and inspect it locally.