best-peer 0.0.26

best-peer 0.0.26

A job's closed box takes half the host's cores and 65536 open files at most and dumps no core, a volume its image declares is a private tmpfs, a container handed a card gets the driver's compute and utility capabilities alone, and the engine's seccomp and AppArmor profiles are named on each container; and a caller of the runtime crate may remove an image it pulled, read the room free where the engine keeps its images, and bound what a pull downloads.

Commits since v0.0.25

• Review: say in run-job which ceilings of the box the operator sets and that no core dump and the driver's capabilities hold for every container, and why an engine set unconfined is still named the built-in profile. (baa9d4d)
• Review: leave a declared volume the spec mounts over to its mount, set the driver's capabilities once, name the built-in seccomp profile only where the engine knows the name, and say what the box and a given-up pull now are. (6a8d342)
• A runtime pull may be bounded by what it downloads and is given up with TooLarge once the layers' sizes pass the bound, so a caller that runs strangers' images can refuse an image too large for the host before it has downloaded it. (2fb1044)
• The runtime removes an image by the reference it was pulled as and says the room free where the engine keeps its images, so a caller that runs strangers' images can refuse a pull that would fill the host's disk and remove each image once its run is over. (f7684dd)
• Name the engine's built-in seccomp profile and AppArmor's docker-default on every container where the engine's info offers them, since a container otherwise rests on daemon defaults that a change to the engine's configuration could drop. (c9f28e5)
• Give a container handed a card the NVIDIA driver's compute and utility capabilities alone, set last in its environment, since an image could otherwise ask the toolkit for every capability of the host's driver. (7d90931)
• Mount a private tmpfs the size of /tmp over each volume a boxed container's image declares, since the engine otherwise makes an unbounded anonymous volume on the host's disk for it. (a3f3c22)
• Hold a job's box to half the host's cores and 65536 open files, and let no container dump a core, since a stranger's job could otherwise take every core, every file handle, and write its memory to the host through the core handler. (85ae447)

Run it

One binary. Download the archive for the machine, check it against SHA256SUMS, unpack it and run best-peer with the environment the README's Run section names; best-peer --version says best-peer 0.0.26. Each archive is here twice, byte for byte the same: under the name with the version, for pinning, and under the name without it, which releases/latest/download/<name> resolves to the newest release, as the README's commands use.

Machine	Archive	Same file, unversioned
Linux x86_64 (glibc 2.35 or newer)	best-peer-0.0.26-x86_64-unknown-linux-gnu.tar.gz	best-peer-x86_64-unknown-linux-gnu.tar.gz
Windows x86_64	best-peer-0.0.26-x86_64-pc-windows-msvc.zip	best-peer-x86_64-pc-windows-msvc.zip
macOS Apple silicon	best-peer-0.0.26-aarch64-apple-darwin.tar.gz	best-peer-aarch64-apple-darwin.tar.gz

Every archive carries a build provenance attestation: gh attestation verify <archive> --repo behavioralstate/best-peer.