mirror of
https://github.com/vhaudiquet/ecrou.git
synced 2026-11-12 22:22:44 +00:00
vhaudiquet
4affe9230c
mke2fs creates and sizes the output file before it populates it, so a build that failed mid-way left a recent-looking image full of zeros at the final name - newer than the tarball, and trusted by the freshness check forever after. The first run after the libarchive fix booted exactly that wreckage: EXT4-fs "Can't find ext4 filesystem". The build now lands in a sibling .part file and renames over the image only on success, and the freshness check additionally requires the ext4 superblock magic (s_magic, at byte 1080) before trusting an existing image - caches already carrying wreckage rebuild over it on the next run instead of needing a manual clean.
ecrou
a small microVM runtime based on libkrun
Try ecrou in the terminal
Installation
ecrou is available as a strictly confined snap:
sudo snap install ecrou
sudo snap connect ecrou:kvm
Usage
$ ecrou run -it ubuntu
root@ecrou-vm-m2glhl:/#
Embed ecrou into your project
ecrou is both a library and a tiny CLI frontend around it. The library is embeddable into any project, allowing to use microVMs easily.
Rust
ecrou is a Rust library, which can just be called:
use ecrou::vm::RunOptions;
use ecrou::NoProgress;
fn main() -> ecrou::Result<std::process::ExitCode> {
let code = ecrou::vm::run(
&RunOptions {
image: "ubuntu:resolute".into(),
command: vec!["uname".into(), "-a".into()],
..RunOptions::default()
},
&NoProgress,
)?;
Ok(std::process::ExitCode::from(code.clamp(0, 255) as u8))
}