Velarx: A container engine with a chain of trust from signature to page reads A developer writing as scrivano.org released Velarx, a container engine written in Rust that builds on composefs and stores every regular file by its fs-verity digest, aiming to verify containers from the image signature down to every page the kernel reads. Velarx keeps containers, images, layers, networks, ports, volumes, secrets and build cache in a single SQLite database, uses one EROFS image per layer instead of per image, and replaces Podman's conmon with a per-container velarx-monitor process; the author benchmarked it against Podman 5.8.9 on a Fedora 44 VM with a 7.4-rc2 kernel, 16 vCPUs and 4 GB of memory. The author said AI was used heavily to prototype the engine, which runs real images and was compared with Podman. Velarx: a container engine with a chain of trust https://www.scrivano.org/posts/2026-11-18-velarx/ Table of Contents For the last few weeks I’ve been working on Velarx, a container engine written in Rust that is built around composefs from the start. I used AI heavily to prototype it, otherwise in a few weeks I wouldn’t have gotten to something that runs real images and that I could compare with Podman. Like composefs, it stores every file by its fs-verity digest. The name comes from the Latin velox , swift, and arx , citadel, and those are the two goals: it has to be fast, and what it runs must be verified from the image signature down to every page the kernel reads. The store the-store Every regular file of every layer is stored once under objects/ , named by its fs-verity digest, as in a composefs repository. A layer is never unpacked into a directory. It is a table of contents and an EROFS image with only the metadata, where each regular file is a stub with trusted.overlay.redirect and trusted.overlay.metacopy pointing to the object and carrying its digest. It is the layout from the composefs sealing post https://www.scrivano.org/posts/2026-06-05-sealing-with-composefs/ , with one EROFS image per layer instead of one per image, so a layer shared by many images is built only once. There isn’t a single fs-verity digest for a file: it depends on the hash algorithm, the Merkle tree block size and the salt. Velarx uses the same parameters as composefs, SHA-256 or SHA-512 over 4096-byte blocks and no salt, and the object names say it, as in fsverity-sha256-12: