Codester demo · Business software
Watches your servers, websites, APIs, and databases from one console on your own machine — metrics, history, and alerts, no monthly fee.
The packaging boot test is deferred: this build machine's container store refused the pinned program image twice with the same write fault (the sandbox's known intermittent store fault — the exact errors are in the test record below), so no container was started and no boot is claimed. What was verified from a fresh extraction of the shipped package: the pinned image exists on the registry, the install files parse, the account file ships with exactly one admin account whose default password the install refuses to start with, and every claim in the listing was checked against the package. Screenshots of the dashboard and a live monitor page will be added when the boot test is closed on a normal Docker host; none are shown here because none were honestly captured.
Real lines from the packaging boot test: the pin and license verified, the image manifest checked, and the exact store fault that deferred the boot — nothing dressed up.
Pin: version 1.9.0, commit a85bd46c18d33130298f0e223bd84ea6e29a17de (clone HEAD, matches the tag) License in clone: Apache License, Version 2.0 (LICENSE 12,587 bytes; NOTICE 173 bytes, both shipped unaltered) Image manifest check: the pinned 1.9.0 image exists on the registry (manifest inspect OK, amd64 + arm64) Boot state: DEFERRED — sandbox store fault. The image could not be pulled writing blob: adding layer ... creating read-only layer with ID "56657e705419...": operation not permitted Error: loading primary layer store data: write /home/hatch/podman-vfs/vfs-layers/.tmp-layers.json502368: operation not permitted loading primary layer store data: write /home/hatch/podman-vfs/vfs-layers/.tmp-layers.json1015027779: operation not permitted