| 1 |
commit: b8a4d55542002bd83d514a1ffe3aeffca417eb4c |
| 2 |
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org> |
| 3 |
AuthorDate: Fri Dec 24 17:05:12 2021 +0000 |
| 4 |
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Fri Dec 24 17:05:12 2021 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=b8a4d555 |
| 7 |
|
| 8 |
containers: Start with a mock config what we target |
| 9 |
|
| 10 |
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org> |
| 11 |
|
| 12 |
containers/config/chroot.toml | 42 ++++++++++++++++++++++++++++++++++++++++++ |
| 13 |
1 file changed, 42 insertions(+) |
| 14 |
|
| 15 |
diff --git a/containers/config/chroot.toml b/containers/config/chroot.toml |
| 16 |
new file mode 100644 |
| 17 |
index 00000000..a766069c |
| 18 |
--- /dev/null |
| 19 |
+++ b/containers/config/chroot.toml |
| 20 |
@@ -0,0 +1,42 @@ |
| 21 |
+# |
| 22 |
+# we always have a section [xxx] where xxx equals the filename |
| 23 |
+# this describes properties of all containers using this method |
| 24 |
+# |
| 25 |
+[chroot] |
| 26 |
+ |
| 27 |
+# does catalyst have to provide bind mounts (e.g. /proc /dev ...)? |
| 28 |
+setup_mounts = true |
| 29 |
+ |
| 30 |
+# does catalyst have to provide process isolation (i.e. unshare)? |
| 31 |
+# setup_namespaces = false |
| 32 |
+ |
| 33 |
+ |
| 34 |
+# do we need to copy files *beyond* the stage definition specific |
| 35 |
+# ones into the isolated filesystem (e.g. /linuxrc)? |
| 36 |
+# support_files = |
| 37 |
+ |
| 38 |
+# do we need to convert the filesystem into an image file and back? |
| 39 |
+setup_image = false |
| 40 |
+ |
| 41 |
+# image pack and unpack commands, if setup_image = true |
| 42 |
+# %c : catalyst support script directory (containers/support) |
| 43 |
+# %D : the root directory of the file system |
| 44 |
+# %F : the filesystem image (i.e., qcow2) |
| 45 |
+# image_pack = ... |
| 46 |
+# image_unpack = ... |
| 47 |
+ |
| 48 |
+# does catalyst have to call setarch? |
| 49 |
+use_setarch = true |
| 50 |
+ |
| 51 |
+# which program call starts up the process? |
| 52 |
+# %c : catalyst support script directory (containers/support) |
| 53 |
+# %D : the root directory of the file system, OR |
| 54 |
+# %F : the filesystem image (i.e., qcow2) |
| 55 |
+# %@ : the command line which is started inside the container |
| 56 |
+command = chroot %D %@ |
| 57 |
+ |
| 58 |
+ |
| 59 |
+ |
| 60 |
+# how precisely further sections should look like is still unclear |
| 61 |
+# * maybe subcases: [chroot.linux32]? |
| 62 |
+# * maybe stage-specific: [chroot.stage1]? |
Archives