Releases
v0.1.1
Compare
Sorry, something went wrong.
No results found
a run ends when its command ends, even with something left running in the background
a failed filter refresh cuts open connections too, and stops VMs if nft itself fails
taps don't answer arp for the host's other addresses
the reaper frees slots held by a stopped wrapper
job input and VM config are private to root and the VM's uid
helpers run as root use a fixed PATH
CRLF and split UTF-8 on a terminal
help text for run
leaving a shell shows no guest kernel reboot line, and the prompt comes back below the session
release tarballs come with build provenance
get.sh: a one-line installer and upgrader
aarch64 tested: both suites pass on ubuntu 24.04 arm, and the README says how to run burner on a mac through lima
the crates are burnervm and burnervm-tui on crates.io, published with every release
ping limits per VM instead of one bucket for all of them
an image's defaults.toml with a typo is an error, not a quiet fallback
a fresh install writes a config with only what you change, so new defaults reach it
You can’t perform that action at this time.