chore(project): change docker compose command

README.md

@@ -247,7 +247,7 @@ docker run -d --name camunda -p 8080:8080 -e SKIP_DB_CONFIG=true \
 
 Starting the Camunda Platform Docker image requires the database to be already 
 available. This is quite a challenge when the database and Camunda Platform are 
-both docker containers spawned simultaneously, for example, by `docker-compose` 
+both docker containers spawned simultaneously, for example, by `docker compose` 
 or inside a Kubernetes Pod. To help with that, the Camunda Platform Docker image 
 includes [wait-for-it.sh](https://github.com/vishnubob/wait-for-it) to allow the 
 container to wait until a 'host:port' is ready. The mechanism can be configured 

test/test.sh

@@ -3,12 +3,12 @@
 DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )
 
 cd ${DIR}
-docker-compose up --force-recreate -d postgres mysql
+docker compose up --force-recreate -d postgres mysql
 ./test-${DISTRO}.sh camunda
 ./test-${DISTRO}.sh camunda-mysql
 ./test-${DISTRO}.sh camunda-postgres
 ./test-${DISTRO}.sh camunda-password-file
 ./test-prometheus-jmx-${DISTRO}.sh camunda-prometheus-jmx
 ./test-debug.sh camunda-debug
-docker-compose down -v
+docker compose down -v
 cd -

test/test_helper.sh

@@ -7,8 +7,8 @@ function _log {
 
 function stop_container {
   docker logs $(container_id)
-  docker-compose kill ${SERVICE}
-  docker-compose rm --force ${SERVICE}
+  docker compose kill ${SERVICE}
+  docker compose rm --force ${SERVICE}
 }
 
 function _exit {
@@ -18,11 +18,11 @@ function _exit {
 }
 
 function start_container {
-  docker-compose up -d --no-recreate ${SERVICE} || _exit 1 "Unable to start compose"
+  docker compose up -d --no-recreate ${SERVICE} || _exit 1 "Unable to start compose"
 }
 
 function container_id {
-  docker-compose ps -q ${SERVICE}
+  docker compose ps -q ${SERVICE}
 }
 
 function grep_log {