You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The location of the data directory cannot be edited when registering a database immediately after raising the container with the monitorr/monitorr image. The location of the data directory is defaulting to ../../../../../../app/userdata/ which is not in the current working directory which does exist in the /config location specified in a compose file, the end result is the data directory (../../../../../../app/userdata/) is within the container itself and is deleted every time the container is either updated or restarted.
The location of the data directory should be editable, or atleast automatically created in the working directory structure specified in the Compose file. Neither of these are possible in the latest monitorr/monitorr image.
Permissions have been checked, /config does get to written to when the container is raised but the issue is the location where the database file should be located.
The text was updated successfully, but these errors were encountered:
Your environment:
Operating system: DSM 7
Monitorr Version: 1.7.6m
Describe your issue:
The location of the data directory cannot be edited when registering a database immediately after raising the container with the monitorr/monitorr image. The location of the data directory is defaulting to ../../../../../../app/userdata/ which is not in the current working directory which does exist in the /config location specified in a compose file, the end result is the data directory (../../../../../../app/userdata/) is within the container itself and is deleted every time the container is either updated or restarted.
The location of the data directory should be editable, or atleast automatically created in the working directory structure specified in the Compose file. Neither of these are possible in the latest monitorr/monitorr image.
Permissions have been checked, /config does get to written to when the container is raised but the issue is the location where the database file should be located.
The text was updated successfully, but these errors were encountered: