From 57f70498af21fafd242ffeb4ce9b5a8b19c22662 Mon Sep 17 00:00:00 2001
From: Devan Carpenter <devan@taler.net>
Date: Thu, 26 Oct 2023 11:15:03 -0400
Subject: sandcastle-ng: make run script show logs

The container is executing "/sbin/init" which has no output, and
prevents us from seeing any logs via the container runtime log
interface.

This change to the run script makes the "podman run" command start the
container in the background, and then proceeds to "exec" journalctl in
the newly running container. Thus allowing us to see the relevant logs
from the system services.
---
 sandcastle-ng/sandcastle-run | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/sandcastle-ng/sandcastle-run b/sandcastle-ng/sandcastle-run
index 1708674..ee98e18 100755
--- a/sandcastle-ng/sandcastle-run
+++ b/sandcastle-ng/sandcastle-run
@@ -37,7 +37,8 @@ fi
 
 SETUP_NAME=${SANDCASTLE_SETUP_NAME:-demo}
 
-exec podman run \
+podman run \
+  -d \
   -p=$SANDCASTLE_PORT_MERCHANT:$PORT_INTERNAL_MERCHANT \
   -p=$SANDCASTLE_PORT_EXCHANGE:$PORT_INTERNAL_EXCHANGE \
   -p=$SANDCASTLE_PORT_LIBEUFIN_BANK:$PORT_INTERNAL_LIBEUFIN_BANK \
@@ -54,3 +55,5 @@ exec podman run \
   --entrypoint /sbin/init \
   "$@" \
   taler-base-all
+
+exec podman exec -it taler-sandcastle journalctl -f
-- 
cgit v1.2.3