fix: bind Java dedup socket directory in Docker

Signed-off-by: Asish Kumar <officialasishkumar@gmail.com>

Author: officialasishkumar

java-dedup/README.md

@@ -35,7 +35,7 @@ Run it with Docker Compose after the Maven package step has created `target/java
 docker compose up --build
 ```
 
-The image runs as a non-root user. For a more restricted container run with a read-only root filesystem, dropped capabilities, `no-new-privileges`, and a writable shared `/tmp` volume for Keploy's Unix sockets:
+The Compose app bind-mounts host `/tmp` into the container so Keploy and the Java SDK use the same Unix socket paths for `/tmp/coverage_control.sock` and `/tmp/coverage_data.sock`. The image runs as a non-root user. For a more restricted container run with a read-only root filesystem, dropped capabilities, `no-new-privileges`, and writable host `/tmp` bind-mounted for Keploy's Unix sockets:
 
 ```bash
 docker compose -f docker-compose.yml -f docker-compose.restricted.yml up --build

java-dedup/docker-compose.restricted.yml

@@ -1,8 +1,6 @@
 services:
   java-dedup:
     read_only: true
-    volumes:
-      - keploy-sockets-vol:/tmp
     cap_drop:
       - ALL
     security_opt:

java-dedup/docker-compose.yml

@@ -10,6 +10,7 @@ services:
       - "8080:8080"
     environment:
       KEPLOY_JAVA_CLASS_DIRS: /app/target/classes
-
-volumes:
-  keploy-sockets-vol:
+    volumes:
+      - type: bind
+        source: /tmp
+        target: /tmp