diff options
| author | BonfaceKilz | 2022-06-14 21:01:00 +0300 |
|---|---|---|
| committer | BonfaceKilz | 2022-06-14 21:02:44 +0300 |
| commit | af01a3ed55a76bb594ed3ad01325c4fa0b30d84b (patch) | |
| tree | aff92d1b1b7ddfc1383e565eebfbac5cdc6f8a0c /topics/systems | |
| parent | 649b4fd55a84180bcd4a00bd4d3cdbe14b6c64ba (diff) | |
| download | gn-gemtext-af01a3ed55a76bb594ed3ad01325c4fa0b30d84b.tar.gz | |
topics: virtuoso: Document how to inspect a system-container
* topics/systems/virtuoso.gmi (Running virtuoso in a guix system
container): Demonstrate, using `nsenter`, how one would inspect a system
container.
Diffstat (limited to 'topics/systems')
| -rw-r--r-- | topics/systems/virtuoso.gmi | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/topics/systems/virtuoso.gmi b/topics/systems/virtuoso.gmi index fba2d50..7fca073 100644 --- a/topics/systems/virtuoso.gmi +++ b/topics/systems/virtuoso.gmi @@ -37,6 +37,12 @@ You can write the above configuration to a file, say virtuoso-os.scm, build a co sudo $(guix system container --network --share=/tmp/virtuoso-state=/var/lib/virtuoso virtuoso-os.scm) ``` +When running the above command, you will be given the container's PID. Should you want to inspect the container, you can run: + +``` +sudo nsenter -t PID -m -p -i -u (readlink -f $HOME/.guix-profile/bin/zsh) +``` + ### Running virtuoso by invoking it on the command line You may also choose to run virtuoso the traditional way by invoking it on the command line. Managing long-running instances started from the command line is messy. So, this method works best for temporary instances. |