Release 2.0

src/jena/fuseki5-docker/Dockerfile

@@ -0,0 +1,17 @@
+FROM stain/jena-fuseki:5.1.0
+
+# Switch to root first (base image ends with USER fuseki)
+USER root
+
+# Install su-exec for switching users (Alpine package)
+RUN apk add --no-cache su-exec
+
+# Copy the wrapper entrypoint
+COPY docker-entrypoint-wrapper.sh /docker-entrypoint-wrapper.sh
+RUN chmod +x /docker-entrypoint-wrapper.sh
+
+# Use our wrapper as the entrypoint (it will switch to fuseki user)
+ENTRYPOINT ["/docker-entrypoint-wrapper.sh"]
+
+# Preserve the CMD from the base image (required when overriding ENTRYPOINT)
+CMD ["/jena-fuseki/fuseki-server"]

src/jena/fuseki5-docker/README.md

@@ -0,0 +1,95 @@
+# Fuseki 5 fixed docker image
+
+This is an extension of `stain/jena-fuseki:5.1.0` docker image for Fuseki 5
+
+## Why the fix ?
+
+When creating a service with docker compose and mounting a volume for Fuseki data, there is a permissions issue.
+
+### The issue
+
+```yaml
+fuseki_tests:
+  image: stain/jena-fuseki:5.1.0
+  container_name: fuseki_tests
+  restart: always
+  volumes:
+    - ./data/fuseki_tests:/fuseki:z
+  ports:
+    - '3040:3030'
+  expose:
+    - '3040'
+  environment:
+    ADMIN_PASSWORD: 'admin'
+```
+
+```
+sylvain@UP222:~/virtual-assembly/activitypods/semapps/src/middleware/tests$ docker compose up -d
+[+] Running 6/6
+ ✔ Network middleware_tests_network  Created                                                                       0.0s
+ ✔ Container redis_middleware_tests  Started                                                                       0.8s
+ ✔ Container ng_tests                Started                                                                       0.8s
+ ✔ Container fuseki_tests            Started                                                                       0.8s
+ ✔ Container arena_tests             Started                                                                       1.5s
+ ✔ Container tripleadmin             Started                                                                       1.5s
+sylvain@UP222:~/virtual-assembly/activitypods/semapps/src/middleware/tests$ docker logs fuseki_tests
+###################################
+Initializing Apache Jena Fuseki
+
+cp: cannot create regular file '/fuseki/shiro.ini': Permission denied
+```
+
+### Temp fix during development
+
+1. That issue could to be fixed with a `chmod 777` from the host computer then relaunching the container.
+
+2. It could also be fixed by forcing the container to run as root :
+
+```yaml
+fuseki_tests:
+  image: stain/jena-fuseki:5.1.0
+  container_name: fuseki_tests
+  restart: always
+  volumes:
+    - ./data/fuseki_tests:/fuseki:z
+  ports:
+    - '3040:3030'
+  expose:
+    - '3040'
+  environment:
+    ADMIN_PASSWORD: 'admin'
+  user: '0:0' # run as root
+```
+
+### Unsatisfying fixes
+
+1. Solution one : implied a manual step, deterrent for devX
+2. Solution two : could lead to security or technical issues as the original image wasn't designed to run as root
+
+## The fix
+
+We extended the docker image to start as root and created an entry point that fixes the permissions on the mounted volume before running the original entrypoint as the fuseki user from the image.
+
+### Build and publish the image
+
+```
+docker build -t semapps/fuseki5-permissions-fix .
+docker push semapps/fuseki5-permissions-fix
+```
+
+### Use the new image
+
+```yaml
+fuseki_tests:
+  image: semapps/fuseki5-permissions-fix
+  container_name: fuseki_tests
+  restart: always
+  volumes:
+    - ./data/fuseki_tests:/fuseki:z
+  ports:
+    - '3040:3030'
+  expose:
+    - '3040'
+  environment:
+    ADMIN_PASSWORD: 'admin'
+```

src/jena/fuseki5-docker/docker-entrypoint-wrapper.sh

@@ -0,0 +1,32 @@
+#!/bin/sh
+set -e
+
+# This script runs as root (because we set USER root in the Dockerfile)
+# Its purpose is to fix permissions on the /fuseki volume before switching
+# to the fuseki user and running the original entrypoint.
+
+# Step 1: Ensure /fuseki directory exists
+# (Docker creates the mount point, but we ensure it exists just in case)
+mkdir -p /fuseki
+
+# Step 2: Change ownership of /fuseki to fuseki:fuseki
+# This ensures the fuseki user (non-root) can write to the directory
+# -R means recursive (applies to all files/subdirs if any exist)
+# 2>/dev/null suppresses error messages if chown fails (shouldn't happen as root)
+# || true ensures the script doesn't fail if chown somehow fails
+chown -R fuseki:fuseki /fuseki 2>/dev/null || true
+
+# Step 3: Ensure the directory is writable by the owner (fuseki user)
+# u+w gives write permission to the user (owner)
+# -R applies recursively to all contents
+chmod -R 777 /fuseki 2>/dev/null || true
+
+# Step 4: Switch to the fuseki user and execute the original entrypoint
+# su-exec is like su but designed for containers (handles signals properly)
+# fuseki:fuseki means user:group
+# The original entrypoint is: /sbin/tini -- sh /docker-entrypoint.sh
+# We use tini (already in base image) to handle signals, and su-exec to switch users
+# The "$@" passes through any arguments (CMD) that were provided
+# The original entrypoint from base image is: /sbin/tini -- sh /docker-entrypoint.sh
+# We use su-exec to switch users, then call tini with the original entrypoint script
+exec su-exec fuseki:fuseki /sbin/tini -- sh /docker-entrypoint.sh "$@"

src/middleware/.eslintrc.json

@@ -90,7 +90,7 @@
     "import/no-unresolved": "off",
     "import/no-useless-path-segments": "warn",
     "import/order": "warn",
-    "jest/no-conditional-expect": "warn",
+    "jest/no-conditional-expect": "off",
     "jsdoc/require-jsdoc": "off",
     "jsdoc/require-param": "off",
     "jsdoc/require-returns": "off",

src/middleware/.nvmrc

@@ -0,0 +1 @@
+22.12.0