[Support] Missing files after restarting docker containers #11650
-
What's your question or issue?A while ago I did a fresh re-install of paperless-ngx using the official recommended docker compose files. But I found that for some reason, after restarting the docker compose project, the Old configuration: New configuration: Other than that I did not change the docker-compose file at all. The problem: after restarting, none of those ~100 files can be found anywhere in my I guess the missing files are caused by changing my mount paths, but I can't figure out where these files are saved now. Stopping/removing containers shouldn't remove any saved documents, right? So they should be somewhere, but how can I find where they are saved? What have you tried?I've looked in my
And I haven't been able to locate the missing files in any of the folders. Paperless-ngx version2.20.3 Host OSContainer Manager in Synology NAS Installation methodDocker - official image System status{
"pngx_version": "2.20.3",
"server_os": "Linux-4.4.302+-x86_64-with-glibc2.41",
"install_type": "docker",
"storage": {
"total": 34528444686336,
"available": 5835381600256
},
"database": {
"type": "postgresql",
"url": "paperless",
"status": "OK",
"error": null,
"migration_status": {
"latest_migration": "guardian.0003_remove_groupobjectpermission_guardian_gr_content_ae6aec_idx_and_more",
"unapplied_migrations": []
}
},
"tasks": {
"redis_url": "redis://broker:6379",
"redis_status": "OK",
"redis_error": null,
"celery_status": "OK",
"celery_url": "celery@ecbf982e8c84",
"celery_error": null,
"index_status": "OK",
"index_last_modified": "2025-12-24T00:00:16.394971-05:00",
"index_error": null,
"classifier_status": "OK",
"classifier_last_trained": "2025-12-24T21:05:09.217680Z",
"classifier_error": null,
"sanity_check_status": "ERROR",
"sanity_check_last_run": "2025-12-21T05:30:35.879779Z",
"sanity_check_error": "192 issues found. Check logs for details."
},
"websocket_connected": "OK"
}Relevant logs or outputNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
You changed the volume mount to a bind mount. Essentially you had your files in one place and then you told paperless to look for them in another location, where they don’t exist. Perhaps do some reading about volume vs bind mounts etc. in docker generally but I assume changing the paths to their previous would restore things |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been automatically closed because it was marked as answered. Please see our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
Thank you both for the tips, I finally managed to figure out how to recover them. This was a bit painful and I'm pretty sure there's a simpler way but leaving my method here in case it helps someone else. I will make sure to always use bind mounts instead of volumes in the future because I like being able to access the files on my host machine, and volumes is too difficult to wrap my head around.
docker volume lsexample of the printout i got: