host and container use same user 1 e2e-test

e2e-tests/storage/backup-restore/docker-compose.yml

@@ -1,6 +1,7 @@
 version: "3.7"
 services:
   nodeA:
+    user: "$USER:$USER"
     image: "${IMAGE_NODE_A:-nutsfoundation/nuts-node:master}"
     environment:
       NUTS_CONFIGFILE: /opt/nuts/nuts.yaml

e2e-tests/storage/backup-restore/run-test.sh

@@ -1,19 +1,20 @@
 #!/usr/bin/env bash
 
 source ../../util.sh
+USER=$UID
 
 echo "------------------------------------"
 echo "Cleaning up running Docker containers and volumes, and key material..."
 echo "------------------------------------"
 docker compose down
 docker compose rm -f -v
-rm -rf ./node-data/*
-rm -rf ./node-backup/*
+rm -rf ./node-data
+rm -rf ./node-backup
 
 echo "------------------------------------"
 echo "Starting Docker containers..."
 echo "------------------------------------"
-mkdir -p ./node-data ./node-backup ./node-backup/vcr/ # 'data' dirs will be created with root owner by docker if they do not exit. This creates permission issues on CI.
+mkdir -p ./node-data ./node-backup/vcr/ # 'data' dirs will be created with root owner by docker if they do not exit. This creates permission issues on CI.
 docker compose up --wait
 
 echo "------------------------------------"
@@ -50,7 +51,8 @@ docker compose stop
 # Copy files not in BBolt DB, so they can be restored. Then empty data dir.
 cp ./node-data/vcr/trusted_issuers.yaml ./node-backup/vcr/
 cp -r ./node-data/crypto ./node-backup
-runOnAlpine "$(pwd):/host/" rm -rf /host/node-data
+rm -rf ./node-data
+#runOnAlpine "$(pwd):/host/" rm -rf /host/node-data
 mkdir ./node-data
 removeNodeDID ./node-A/nuts.yaml
 # Restart node, assert node data is empty