summaryrefslogtreecommitdiff
path: root/topics/systems/virtuoso.gmi
diff options
context:
space:
mode:
Diffstat (limited to 'topics/systems/virtuoso.gmi')
-rw-r--r--topics/systems/virtuoso.gmi6
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.