Anyone running/moved to 2.0.0. on Synology successfully?

[stewartdoyle]

Hi everyone
I suspect this should really be an 'issue' but this is only my second ever post on Github and I'm not the most experienced docker/container manager user!
I was running version 1.9.3 successfully and I was very impressed with it. I installed reitti as a project within container manager on my Synology DS723+ running DSM 7.2.2-72806 Update 4
I stopped the project and updated the container image to 2.0.0 - however I made the mistake of not reading the change notes first and restarted the project. When it failed I added the new line for the /data/ folder. It still failed, all the conainers started but then the main reitti container (reitti-reitii-1) stopped. I then noticed some extra lines in the new docker-compose.yaml file and installled that - still the main reitti container stopped after starting.
I then tried a brand new install of reittii, but this displayed the same behaviour. The project starts but the main reitti container starts and then stops. I added LOGGIN_LEVEL: DEBUG under the environment strings and these seem to be the lines where it is crashing...

I'm not sure where the real log lives, but here is the full line of one of the above
2025-11-02T09:08:12.015Z WARN 1 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'memoryBlockController' defined in URL [jar:nested:/app/app.jar/!BOOT-INF/classes/!/com/dedicatedcode/reitti/controller/MemoryBlockController.class]: Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'memoryService' defined in URL [jar:nested:/app/app.jar/!BOOT-INF/classes/!/com/dedicatedcode/reitti/service/MemoryService.class]: Unsatisfied dependency expressed through constructor parameter 5: Error creating bean with name 'memoryBlockGenerationService' defined in URL [jar:nested:/app/app.jar/!BOOT-INF/classes/!/com/dedicatedcode/reitti/service/MemoryBlockGenerationService.class]: Unsatisfied dependency expressed through constructor parameter 3: Error creating bean with name 'immichIntegrationService' defined in URL [jar:nested:/app/app.jar/!BOOT-INF/classes/!/com/dedicatedcode/reitti/service/integration/ImmichIntegrationService.class]: Unsatisfied dependency expressed through constructor parameter 3: Error creating bean with name 'storageService' defined in URL [jar:nested:/app/app.jar/!BOOT-INF/classes/!/com/dedicatedcode/reitti/service/StorageService.class]: Failed to instantiate [com.dedicatedcode.reitti.service.StorageService]: Constructor threw exception

---

I didi think I might have caused an inconsistent state by not updating the docker-compose, but I can't understand why a fresh install is failing - unless the older version is interfering with the new?
So, I'm just wondering if anyone has seen a general problem running the new version under container manager/Synology or am I just doing something wrong?

I'd be very grateful for any assistance
Best wishes
Stewart

[dgraf-gh]

Hi @stewartdoyle,

this looks like the folder which you mounted is not writeable to the reitti user. This is typical the user with ID 1000 and group id 1000. Make sure that on the host the folder is writable by this user.

I do not use synology and can't give you any instructions how to do it. On a typical Linux installation i would do sudo chown 1000:1000 <your path>

When this is fixed, reitti should start.

Since you are not the first encountering this issue i will update the readme.

I considered to fix the permissions on startup of reitti, but decided against it because i could not decide if the container should mess with the host system. Probably not.

[stewartdoyle]

Thanks very much, that has fixed the problem. Luckily, I knew how to use putty to get into the synology device as an admin user, then used 'sudo bash' and navigated to the reitti folder in the docker area and ran 'chown -R 1000:1000 *-data'
Thanks again,
Stewart