User:Ajak/systemd-nspawn for Development and Update Automation

WIP
Unpack a stage3 into a directory which will become an nspawn container in. As is in the process of being fixed (and is for arm64),  can be used.

Create an nspawn configuration for the machine in (the filename should be the same as the directory name created in the previous step).

Start the container manually once to disable the root password and the service.

Start and enable the container to start at boot (but enabling doesn't seem to work for me, haven't investigated).

Usage
To use the container, you can simply login via the facility:

Any changes made inside of the container will be persistent. When doing things like ebuild development, this is not necessarily desirable.

To use the container ephemerally (such that changes made while the container is in use are lost afterwards), manually using is necessary: