summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDevan Carpenter <devan@taler.net>2023-10-26 11:15:03 -0400
committerDevan Carpenter <devan@taler.net>2023-12-04 09:54:36 -0500
commit57f70498af21fafd242ffeb4ce9b5a8b19c22662 (patch)
tree7dc9cd7677cf03d8d4522a69b6aac3a59316b227
parentf61f808808e1239df2f3d50f8f929d7f3499d89d (diff)
downloaddeployment-57f70498af21fafd242ffeb4ce9b5a8b19c22662.tar.gz
deployment-57f70498af21fafd242ffeb4ce9b5a8b19c22662.tar.bz2
deployment-57f70498af21fafd242ffeb4ce9b5a8b19c22662.zip
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.
-rwxr-xr-xsandcastle-ng/sandcastle-run5
1 files changed, 4 insertions, 1 deletions
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