From d0f5bae2c42ba5a4191bf56064e5cf22b8456efb Mon Sep 17 00:00:00 2001
From: Pjotr Prins
Date: Wed, 6 Mar 2024 07:57:50 -0600
Subject: Edits Pjotr

---
 topics/systems/fire-up-genenetwork-system-container.gmi | 11 +++++++++++
 1 file changed, 11 insertions(+)

(limited to 'topics')

diff --git a/topics/systems/fire-up-genenetwork-system-container.gmi b/topics/systems/fire-up-genenetwork-system-container.gmi
index bb2e55e..11cd9d2 100644
--- a/topics/systems/fire-up-genenetwork-system-container.gmi
+++ b/topics/systems/fire-up-genenetwork-system-container.gmi
@@ -14,6 +14,7 @@ We have the following check list
 * [ ] Create a system definition
 * [ ] Fire up container and get a shell inside using nsenter
 * [ ] Start mariadb
+* [ ] Start redis
 
 ## Create a system definition
 
@@ -129,3 +130,13 @@ herd start mysql
 | db_webqtl_s               |
 +---------------------------+
 ```
+
+Once I got this working, however, I decided to run mariadb on the base system instead (outside the container). The same with redis (see below).
+
+# Start redis
+
+After adding the default redis-service make sure the database is mounted on /var/lib/redis. `herd status` in the container will tell redis is running.
+
+Note that, again, file permissions may prevent redis from running. Debug output appears in /var/log/messages.
+
+The way to deal with this is chown in the activation stage. The alternative is to run a service directly on the host machine.
-- 
cgit v1.2.3