I don't use this anymore, and there are better and still-maintained
alternatives (Docker, vagrant, ansible, etc.) and I no longer feel like
maintaining it.
This appliance hosts the Gentoo Virtual Appliance[1] tool. Now you can
build the thing that builds the thing that builds the things.
Note that you cannot (yet) run this inside of a systemd (or Docker)
container (without giving it special privs), but I'm working on that. It
should at least be possible to build stage4s with it.
[1] https://bitbucket.org/marduk/virtual-appliance
This appliance runs the docker[1] service. Now you have something to run
your Gentoo Virtual Appliances images in ;-)
Note this appliance uses its own kernel config, because docker won't run
with the default configs.
[1] https://www.docker.com/
For some reason we had to add "setuptools" to emerge even though we're
installing virtualenv. Does virtualenv not install setuptools anymore or
was this just a bug?
When I switched over from openrc to systemd I was being lazy and took
advantage of the fact that /etc/local.d still gets run as usual on
Gentoo. This commit finally does a proper(-ish) systemd startup using
(3) unit files.
The nullok flag is needed in order to allow root to have an empty password
(forced to set on first login).
The sha512 flag is just to ensure passwords are cyptographically secure.
Although the documentation says it defaults to False, it seems to be getting
set to True in my deployments. This explicitely sets it to false and also
sets the TIMEZONE to UTC.
This change converts the appliances from openrc to systemd. In addition,
systemd needs to at least be be installed on the build machine as we now
use systemd-nspawn instead of chroot/bind mounts do to the fact that
systemd-nspawn is much more robust and lese prone to errors. In addition:
* All stage4 tarballs and images are now stored in the images/ directory by
default.
* A package dir is now required and is set up in the packages/ directory by
default.
* The portage directory is not unpacked in the chroot every time anymore
and is instead bind-mounted from a directory by systemd-nspawn. This is
the portage/ directory by default.
* In addition there is a distfiles/ directory (by default) which is
bind-mounted in the chroot. It does what you'd probably expect.
* The Makefile learned new target, eclean, which will run eclean-dist and
eclean-pkg to clean out obsolete distfiles and binary packages.
* The REMOVE_PORTAGE_TREE option is removed as portage is no longer
installed.
* The unused/untested PRUNE_CRITICAL functionality has been removed. I
have no idea if it worked and if it didn't I didn't want to fix it.
* As appliances are always using systemd, UDEV is no longer optional.
* Timezones and hostnames are now handled by systemd (systemd-firstboot).
* Stage4 tarballs are now directly importable as systemd containers (and
probably docker too though I haven't tested that yet).
* A number of packages (for example dhcpd, acpid) have been removed from the
appliances when systemd provides equivalent functionality.
* We no longer override etc-update.conf. There's no reason.
* A number of Makefile targets, checkpoints, temp files, etc have been
removed as they are no longer needed.
Instead of having everything in the root directory, split them in seperate
directories (appliances, scripts, & configs). This makes things a little
tidier.
Also added a now Makefile target, appliance-list, that prints a list of the
available appliances. The split directory change made this easier.
Albert Hopkins