Add ability to produce self-contained builds
-
Set up a root from builddeps via moss
-
Call moss-container
to buildpackage.stone
-
Use mason
command to buildpackage.stone
in the current environment -
Divide responsibility of boulder
andmason
in the same project (args[0] match based) code-wise -
Add ability to pass in bind-mount options to boulder
(and pass them on tomoss-container
) via the CLI
Bind mount Notes:
Ikey Doherty: basically moss-containers is passed some arbitrary set of bind mounts to do
Ikey Doherty: and boulder tells moss-container what they are
Ikey Doherty: saves boulder needing to make any mount calls
Ikey Doherty: then by the time we call mason inside the container, the full working environment is in place
Ikey Doherty: "bind|b", "Set up bind mounts", &binds);
Ikey Doherty: which is string[string]
Ikey Doherty: getopt processes that with "-b key=value"
Ikey Doherty: and multiple b is allowed
Ikey Doherty: i.e. -b one=one -b two=two
Ikey Doherty: all we need to do then is verify the source exists, recursively mkdir the target, and bind mount it
General Notes:
Ikey Doherty: So I feel I want moss triggers and glibc nss alt files
Ikey Doherty: Then moss container would dynamically find the right uid to drop to
Edited by Ikey Doherty