Where Does BlendOS Store System Config?
BlendOS declares the whole system in /system.yaml at the filesystem root, managed by the akshara tool.
Last updated
BlendOS keeps host intent in a single file at the filesystem root. That file names the track for the desktop and the extra packages, with service toggles beside them. There is no blend directory under /etc to search, and writes to binaries revert on update because the host is immutable and managed by its update tool.
Edits belong in the host file as root, followed by an update run to apply them. Keep a copy before switching tracks or editing package lists, since the file is small and a saved copy restores the prior setup. Day to day work stays in podman containers through the blend CLI or in WayDroid, while the host file itself covers the base system only.
Where BlendOS stores this, by platform
/system.yaml
Declarative host config at root, not under /etc. Parsed by akshara on update. Back it up before track or package changes.
Frequently asked questions
How do I add packages to BlendOS?
Edit /system.yaml as root, adding package names under packages and repos under impl tracks like gnome or plasma. Run the akshara update afterwards. User containers are separate; this file is the host only.
Where do BlendOS containers live?
Through podman containers via the blend CLI (enter, exec, create-container). Android apps run through WayDroid. The host stays declarative; mutable work belongs in containers.
Notice an outdated path? Let us know.