diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-16 17:44:30 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-16 17:44:30 +0000 |
| commit | 71ba08c6d93457b2b55dcd1bf7631dea989d6859 (patch) | |
| tree | 844d51d2c3a0c14b48263ad7ba34d78014fbd835 /genenetwork/services/test/julia_notebook_http_tests.py | |
| parent | 6bab9efc8f1e7338548a61c379f57571657f5488 (diff) | |
| download | gn-machines-main.tar.gz | |
A container's store item is /gnu/store/<hash>-run-container for all of them,
and the name is hard-coded inside Guix (`(gexp->script "run-container" ...)'
in gnu/system/linux-container.scm), so it cannot be changed here. A GC root
can: containers/cgit-container -> /gnu/store/<hash>-run-container gives the
hash a name to ask for, pins the container against a guix gc, and lets a log
line or a person say "cgit-container" and mean one store item.
./root-containers.sh # all eight
./root-containers.sh cgit-container # one
./root-containers.sh --list # name -> store item
The root's name is the container's own host-name, never an abbreviation: the
same word then appears in --list, in /etc/issue and here. The per-container
deployment flags live in this file and are not left to a convention, because
the wrong flags build a container that boots and then cannot see its data (an
--expose/--share of a path that does not exist is dropped silently).
Two things it has to get right, both measured: `guix build --root' refuses to
replace an existing root ("failed to create GC root: File exists"), so the old
symlink is removed first and a non-symlink is refused rather than deleted; and
the name has to be usable where the hash was, so the client resolves a root
through File.realpath before validating it (run-guix-container).
Diffstat (limited to 'genenetwork/services/test/julia_notebook_http_tests.py')
0 files changed, 0 insertions, 0 deletions
