fix(docker): correct Dockerfile path and image tag in VMs scripts

Fixes two issues reported on PR #445:

- VMs/buildDockerImage.sh used `.` as build context with no --file,
  so running the script from the repo root made buildx look for
  ./Dockerfile (which does not exist). Switch to explicit
  --file VMs/Dockerfile and context VMs, matching the paths used
  by .github/workflows/docker-publish.yml.

- VMs/runDockerImage.sh still referenced the old `benchmark` image
  tag, but the buildx rewrite in c68a62b publishes
  `owasp/benchmark:latest`. Update the tag so `docker run` finds
  the freshly-built image.

Reported-by: @darkspirit510

Author: TheAuditorTool

VMs/buildDockerImage.sh

@@ -16,13 +16,17 @@ fi
 
 # Build and push a multi-architecture image in one step.
 # --push is required because multi-arch manifest lists cannot be loaded into
-# the local daemon. The image is pushed directly to Docker Hub.
+# the local daemon. The image is pushed directly to Docker Hub, so this
+# script requires `docker login` first.
+# Run this script from the repository root; paths below mirror the CI
+# workflow (.github/workflows/docker-publish.yml).
 echo "Building ${IMAGE}:${TAG} for ${PLATFORMS} ..."
 docker buildx build \
   --platform "$PLATFORMS" \
   --tag "${IMAGE}:${TAG}" \
+  --file VMs/Dockerfile \
   --push \
-  .
+  VMs
 
 echo "Done. Published ${IMAGE}:${TAG} for ${PLATFORMS}."
 

VMs/runDockerImage.sh

@@ -1,2 +1,2 @@
-docker run -t -i -p 8443:8443 --rm benchmark /bin/bash -c "git pull && ./runRemoteAccessibleBenchmark.sh"
+docker run -t -i -p 8443:8443 --rm owasp/benchmark /bin/bash -c "git pull && ./runRemoteAccessibleBenchmark.sh"