btb205

understood. I looked in an pold backup of the app data folder and could see that the runtime-folder hat actuall 2 jre version, jre17 and jre21. Maybe this caused the problem .

sure, makes perfect sense. When i was checking the appdata folder (before the actual cleanup) i could see the error message was actually right. There was no /bin/jre... in my /bin folder of the app data. In fact there was no jre folder at all. I found something in the runtime section. I just could not make a sense how it should have been disappeared from there. So the idea behin my last question was to figure out, if there is a way to influence at which point the system looks for the jre folder. In the newly created appdata folder there is no jre folder present as well at this point, but this seem not to be a problem.

thanks for the hint and the update Quick question though: where would i remove the jre path form the container? I could not find it to be defined in the unraid container definition (where I enter the path to appdata, port. etc.), independent if i switched to advanced view or not. I guess a change within the container itself (so login into the container with bash) would not survice the container is rebuild the container from and updated image, right?

Just an FYI, I solved my issue by - completly deleting the appdata folder for the container - reinstalled the container from scratch I still do not undertstand what caused the issu in the first place , but after eeting the container complety reinstall itseld and setup the appdata folder from scratch, the issue is gone.

Hi, I realized a weird behaviour with the portfolio-performance container today. The container was installed and automatically updated from the repsective unraid image https://hub.docker.com/r/ich777/portfolio-performance. So far it ran without any problems, but today when starting up, I saw unexpected errors in the VNC session. When I now try to login using the WebGUI, i see an error message, pointing to a missing java version in the path variable. This is a new error, that i have not seen so far. I tried to reinstall the container (including deleting the image), as well as going to a backup a couple of days old, I created with the "Backup/Restore-Appdata" tool. I could see that the container image was updated on the 3rd of December by ich777, but unfortunaly I do not have a backed up version of the image before this time anymore. Could it be that the new container image might have a bug? Or did I overlook something else. Thanks and KR Thomas