-
Notifications
You must be signed in to change notification settings - Fork 28
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Is there an existing issue for this?
- I have searched the existing issues and did not find anything similar.
Bug Description
Description
Settings created within the Rclone Manager UI, specifically sync profiles, cron schedules, and tasks are not persisting after the container is stopped and removed via docker-compose down. While the rclone remotes (rclone.conf) remain intact, all app-specific configurations disappear. The UI returns to a "fresh" state. All profiles and tasks are gone. Only the storage remotes (loaded from the external rclone.conf volume) are still present.
Operating System
Linux
OS Version
Linux omv 6.12.57+deb12-amd64
App Version Type
Headless (Web server accessed via browser)
App Version Number
0.2.0
RClone Version
1.73.0
Steps to Reproduce
- Launch Rclone Manager using docker-compose up -d.
- Access the Web UI and create a New Profile or a Scheduled Sync Task.
- Verify the task is saved and visible in the dashboard.
- Run docker-compose down on the host machine.
- Run docker-compose up -d again.
- Return to the Web UI.
Expected Behavior
All previously created profiles, cron jobs, and sync tasks should be restored and visible, as they should be stored in a persistent database.
Relevant Logs
Screenshots/Recordings
No response
Additional Context
The issue does not occur during a docker compose stop
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working