Make a root filesystem¶
A root filesystem is the finished packages of one or more builds, installed into an empty directory and saved as a tarball: what will be inside an image, a virtual machine or a disk. Builds > RootFS builds, then +.
Field |
What to put |
|---|---|
Name |
For example |
Package builds |
The builds whose packages go in. Each must have succeeded. |
Portage tree |
The same tree as the build, or leave it empty to take the build’s. |
Portage configs |
Leave empty: the root uses the build’s config, so it is installed with the same USE flags. |
Keep the result in |
A binary repository with an upload proxy: where the tarball is kept. Use your own. |
Nothing is compiled here: the packages are taken from your repository (this is why Take ready-made packages (pull from) with Copy pulled matters) and installed. It takes a few minutes. When it has Succeeded, the root is a tarball in your repository, with a lock file that lists exactly what is in it.
If it fails, a Retry button next to Delete puts it back to Pending.
Use the image¶
A root filesystem is not bootable by itself. Its page has a section Use the image with instructions for taking it to a cloud or a virtual machine: Amazon (AMI), QEMU and Google Cloud. If the image has a kernel and a boot loader, it will boot.
Security¶
A root is scanned for known vulnerabilities from its lock file, which is the authoritative list of what is inside (see Security: vulnerabilities in what you build).