From 5a9f55d3d534a7e7936f61d6b3f75f971869b5ac Mon Sep 17 00:00:00 2001 From: Honza Horak Date: Thu, 4 Jan 2024 17:12:00 +0100 Subject: [PATCH] Gracefully shut down the original container With keeping the container running, we see SELinux error messages and sudden crash of the PostgreSQL container. Let's properly shut down the container before using its volume privately mounted into a different container. Background: podman's :Z modificator for volumes works the way that the latest container run with the same volume directory mounted with :Z modificator has access, the previous containers are kept running, but access to the shared directory is suddenly removed. That caused the first instance of PostgreSQL server to crash with SIGSEGV actually, while triggering some SELinux error message during that. --- test/run_test | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/test/run_test b/test/run_test index 9dc6929b..a3269624 100755 --- a/test/run_test +++ b/test/run_test @@ -634,6 +634,13 @@ $volume_options echo " Changing passwords" + echo "Kill the previous container and create a new one" + local cidfile=$CID_FILE_DIR/"${name}" + docker kill $(cat $cidfile) + docker rm -f $(cat $cidfile) + # Don't forget to remove its .cid file + rm $cidfile + DOCKER_ARGS=" -e POSTGRESQL_DATABASE=${database} -e POSTGRESQL_USER=${user}