issue launching reitti

[wjansenw]

Hi,
I have an issue trying to launch reitti.

• I switched the postgis to image imresamu/postgis:17-3.5-alpine as I'm running on odroid n2+. That is fine, and not causing issues.
• I disabled Photon container (for now)

All containers start except the reitti one:

reitti-1    | 2025-12-04T10:13:51.392287328Z Exception in thread "main" java.lang.reflect.InvocationTargetException
reitti-1    | 2025-12-04T10:13:51.392447752Z 	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
reitti-1    | 2025-12-04T10:13:51.392540047Z 	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
reitti-1    | 2025-12-04T10:13:51.392549465Z 	at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:106)
reitti-1    | 2025-12-04T10:13:51.392576591Z 	at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:64)
reitti-1    | 2025-12-04T10:13:51.392626218Z 	at org.springframework.boot.loader.launch.JarLauncher.main(JarLauncher.java:40)
reitti-1    | 2025-12-04T10:13:51.392734848Z Caused by: java.lang.NoClassDefFoundError: org/slf4j/spi/SLF4JServiceProvider
reitti-1    | 2025-12-04T10:13:51.392781058Z 	at org.apache.commons.logging.LogAdapter$Slf4jAdapter.createLocationAwareLog(LogAdapter.java:121)
reitti-1    | 2025-12-04T10:13:51.392846353Z 	at org.apache.commons.logging.LogAdapter.createLog(LogAdapter.java:95)
reitti-1    | 2025-12-04T10:13:51.392906689Z 	at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:67)
reitti-1    | 2025-12-04T10:13:51.392949858Z 	at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:59)
reitti-1    | 2025-12-04T10:13:51.392972734Z 	at org.springframework.boot.SpringApplication.<clinit>(SpringApplication.java:202)
reitti-1    | 2025-12-04T10:13:51.393000818Z 	at com.dedicatedcode.reitti.ReittiApplication.main(ReittiApplication.java:13)
reitti-1    | 2025-12-04T10:13:51.393048821Z 	... 5 more
reitti-1    | 2025-12-04T10:13:51.393197702Z Caused by: java.lang.ClassNotFoundException: org.slf4j.spi.SLF4JServiceProvider
reitti-1    | 2025-12-04T10:13:51.393246205Z 	at java.base/java.net.URLClassLoader.findClass(Unknown Source)
reitti-1    | 2025-12-04T10:13:51.393273706Z 	at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
reitti-1    | 2025-12-04T10:13:51.393321208Z 	at org.springframework.boot.loader.net.protocol.jar.JarUrlClassLoader.loadClass(JarUrlClassLoader.java:107)
reitti-1    | 2025-12-04T10:13:51.393387128Z 	at org.springframework.boot.loader.launch.LaunchedClassLoader.loadClass(LaunchedClassLoader.java:91)
reitti-1    | 2025-12-04T10:13:51.393403587Z 	at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
reitti-1    | 2025-12-04T10:13:51.393434088Z 	... 11 more

I'm attaching my docker-compose and the log files.

docker-compose.yml
logs.txt

I have no idea how to fix this... If you need anything else to troubleshoot, let me know...

Looking forward to play with Reitti...
Tnx,
Wim

[dgraf-gh]

Hi @wjansenw,

I have no idea how to fix this... If you need anything else to troubleshoot, let me know...

Me neither :D Never have seen this one.
This class should be bundled inside one of the jars and if it would not be there, then all installations would fail.

Let me investigate that a little bit.

[wjansenw]

Resorted to claude.ai for assistance... Managed to get the container launched... Not sure what is the best way to fix it, or what is the real issue.
Note: running on Odroid n2+

This is what Claude suggested as solution (after several back and forths):

Problem

The current Docker setup doesn't support ARM64 architecture (e.g., Odroid N2+, Raspberry Pi, Apple Silicon). The pre-built image fails to start with classpath errors, and the Dockerfile expects a pre-built JAR file which makes it difficult to build locally for ARM64 platforms.

Solution

Implement a multi-stage Docker build that:

1. Compiles the application from source in the build stage
2. Creates a lean runtime image in the final stage
3. Works on both x86_64 and ARM64 architectures

Changes Needed
Replace the current Dockerfile with a multi-stage build:

# Build stage - Use Java 23 (supports unnamed variables as preview feature)
FROM maven:3.9-eclipse-temurin-23-alpine AS build
WORKDIR /build
COPY pom.xml .
COPY src ./src
# Build with skip git plugin
RUN mvn clean package -DskipTests -Dmaven.compiler.release=23 -Dmaven.gitcommitid.skip=true

# Runtime stage - Use Java 23 to match
FROM eclipse-temurin:23-jre-alpine
LABEL maintainer="dedicatedcode"
LABEL org.opencontainers.image.source="https://github.com/dedicatedcode/reitti"
LABEL org.opencontainers.image.description="Reitti - Personal Location Tracking & Analysis"
LABEL org.opencontainers.image.licenses="MIT"

# Create a non-root user and group
RUN addgroup -S reitti -g 1000 && adduser -S reitti -u 1000 -G reitti

# Set environment variables
ENV SPRING_PROFILES_ACTIVE=docker
ENV APP_HOME=/app
ENV DATA_DIR=/data

# Create application directory
RUN mkdir -p $APP_HOME && \
    chown -R reitti:reitti $APP_HOME

WORKDIR $APP_HOME

# Copy the application jar from build stage
COPY --from=build --chown=reitti:reitti /build/target/*.jar $APP_HOME/app.jar

# Create a script to start the application with configurable UID/GID
RUN echo '#!/bin/sh' > /entrypoint.sh && \
    echo 'if [ -n "$APP_UID" ] && [ -n "$APP_GID" ]; then' >> /entrypoint.sh && \
    echo '  echo "Changing reitti user/group to UID:$APP_UID / GID:$APP_GID"' >> /entrypoint.sh && \
    echo '  apk add --no-cache shadow' >> /entrypoint.sh && \
    echo '  groupmod -g $APP_GID reitti' >> /entrypoint.sh && \
    echo '  usermod -u $APP_UID reitti' >> /entrypoint.sh && \
    echo '  chown -R reitti:reitti $APP_HOME' >> /entrypoint.sh && \
    echo 'fi' >> /entrypoint.sh && \
    echo 'mkdir -p $DATA_DIR' >> /entrypoint.sh && \
    echo 'chown -R reitti:reitti $DATA_DIR' >> /entrypoint.sh && \
    echo 'exec su-exec reitti java --enable-preview $JAVA_OPTS -jar $APP_HOME/app.jar "$@"' >> /entrypoint.sh && \
    chmod +x /entrypoint.sh

# Expose the application port
EXPOSE 8080

# Add healthcheck
HEALTHCHECK --interval=5s --timeout=3s --start-period=1s --retries=20 \
  CMD wget --no-verbose --tries=1 --spider http://localhost:8080/actuator/health || exit 1

# Install su-exec for proper user switching and wget for healthcheck
RUN apk add --no-cache su-exec wget

# Run as root initially to allow UID/GID changes
USER root

ENTRYPOINT ["/entrypoint.sh"]

In addition, I had to remove the src/ from the .dockerignore file (I removed the file completely I believe)

After building, it generated a working container, and I managed to launch the services. Have not yet tested the application, but the login screen was available, and managed to create the first user.

Regards,
Wim

[dgraf-gh]

In addition, I had to remove the src/ from the .dockerignore file (I removed the file completely I believe)

Makes sense since your are building the app inside a docker container and this only works with the src.

I am glad you found a solution, but to be honest - i do not see the difference to that what we are doing in https://github.com/dedicatedcode/reitti/blob/main/.github/workflows/release.yml

We build the application here at line 32. That is the basically the same as your RUN mvn clean package -DskipTests -Dmaven.compiler.release=23 -Dmaven.gitcommitid.skip=true

      - name: Build
        run: mvn verify -DskipTests

Then we build the docker image with these platforms amd64,linux/arm64
at

reitti/.github/workflows/release.yml

Lines 61 to 66 in f32dcc6

	- name: Build and push
	uses: docker/build-push-action@v6
	with:
	platforms: linux/amd64,linux/arm64
	context: .
	push: true

and finally push them.

The only difference I see is the jre-23 vs jre-24

[wjansenw]

If we can trust Claude (I haven't done further investigation on this):

The Maven image for Java 24 on ARM64 appears to be broken or incompatible. Let's use a different approach - use a Java 24 base image and install Maven manually, or use Java 21/23 which have better ARM64 support.

[dgraf-gh]

Maybe Claude knows more than us :D
I initially searched for the error but could not find any meaningful results.

As I said, im glad you found a solution. Since i am preparing the next release I will be updating to Java 25 now. Maybe this solves then that issue in general.