Data Persistence to CIFS #3108

Open
opened 2026-02-28 03:18:20 -05:00 by deekerman · 0 comments
Owner

Originally created by @chrisfore on GitHub (Feb 7, 2024).

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I have used a volume mount to save the /data folder to a cifs mount. The container boots without issue and the kuma.db file and a few other folders are written to the mount. When I redeploy the container with the same mount point, all configuration (monitors, admin settings, notifications) are lost/not persistent.

📝 Error Message(s) or Log

no messages in the error.log

🐻 Uptime-Kuma Version

1.23.10

💻 Operating System and Arch

ubuntu 22.04 with docker engine

🌐 Browser

brave

🖥️ Deployment Environment

  • Runtime: ubuntu 22.04 - Docker version 25.0.1, build 29cf629
  • Database:
  • Filesystem used to store the database on: cifs to all flash nas
  • number of monitors: 8
Originally created by @chrisfore on GitHub (Feb 7, 2024). ### ⚠️ Please verify that this question has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I have used a volume mount to save the /data folder to a cifs mount. The container boots without issue and the kuma.db file and a few other folders are written to the mount. When I redeploy the container with the same mount point, all configuration (monitors, admin settings, notifications) are lost/not persistent. ### 📝 Error Message(s) or Log no messages in the error.log ### 🐻 Uptime-Kuma Version 1.23.10 ### 💻 Operating System and Arch ubuntu 22.04 with docker engine ### 🌐 Browser brave ### 🖥️ Deployment Environment - Runtime: ubuntu 22.04 - Docker version 25.0.1, build 29cf629 - Database: - Filesystem used to store the database on: cifs to all flash nas - number of monitors: 8
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3108
No description provided.