- Container runtime build path documented.
docs/containers.md now walks through what it takes to
ship Docker, containerd, and runc on a musl yoe rootfs — why prebuilt "static"
binaries don't work, the per-component build breakdown, and how cgo units like
runc plug into yoe's existing Go toolchain andtoolchain-muslcontainer via
depsinstead of needing a new Go+GCC container image. - Rename
debugunits todev. - Expand roadmap. Reorganized as a pointer index into the
design docs, with new sections for the app-developer build/deploy loop,
hardware access, testing, self-hosting, and distribution variants. - New testing design doc at docs/testing.md covers the
plannedyoe testdriver, build-time package QA, on-device upstream tests
(Yoctoptestanalog), image smoke tests, and CI integration. - Kernel modules now ship in images — the
linux,linux-rpi4, and
linux-rpi5units previously built only the in-tree kernel image, so drivers
compiled as loadable modules (Wi-Fi, USB, sound, many filesystems) were
silently dropped. Modules are now built and installed to
/lib/modules/<kver>/in the rootfs, somodprobefinds them at runtime. - Fix rPI4 builds package arch did not match what apk was expecting.
To update, run: yoe update
Or download the binary for your architecture and place it in your PATH.
Note: Yoe-NG is in heavy development. We recommend cleaning your build directory and re-creating projects (yoe init) with each new release.