From af01a3ed55a76bb594ed3ad01325c4fa0b30d84b Mon Sep 17 00:00:00 2001
From: BonfaceKilz
Date: Tue, 14 Jun 2022 21:01:00 +0300
Subject: 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.
---
 topics/systems/virtuoso.gmi | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'topics/systems')

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.
-- 
cgit v1.2.3