[GH-ISSUE #14076] issue: Persistent Data Remnants in Docker Volume After Deleting Knowledge Base Files in Open-WebUI #136858

Closed
opened 2026-05-25 05:35:38 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @mokieli on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14076

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.10

Ollama Version (if applicable)

No response

Operating System

Windows11

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have listed steps to reproduce the bug in detail.

Expected Behavior

When a file collection is deleted from the knowledge base via the WebUI, all associated files — including both the original text files in the uploads folder and the parsed data in the vector_db folder — should be completely removed from the Docker volume. Additionally, executing "Reset Upload Directory," "Reset Vector Storage/Knowledge," and "Rebuild Knowledge Base Vectors" should fully clear any residual vector data and free up storage space.

Actual Behavior

After deleting a file collection from the knowledge base via the WebUI, the uploads folder and vector_db folder inside the Docker volume still retain the original text files imported into the knowledge base and the parsed data files. Moreover, the parsed data files in vector_db take up a significant amount of storage space. Performing 'Reset Upload Directory', 'Reset Vector Storage/Knowledge', and 'Rebuild Knowledge Base Vectors' in the Admin Settings under the Document section does not remove the residual data in vector_db; only the contents of the uploads folder are cleared.

Steps to Reproduce

  1. Launch Open-WebUI and navigate to the Knowledge Base section.
  2. Create a new knowledge base or use an existing one.
  3. Upload a text file to the knowledge base via the WebUI.
  4. Wait for the file to be fully parsed and processed.
  5. Delete the uploaded file from the knowledge base through the WebUI interface.
  6. Access the Docker volume associated with Open-WebUI.
  7. Navigate to the uploads folder within the volume and verify that the original file has been removed.
  8. Navigate to the vector_db folder and observe that the parsed vector data files related to the deleted file still remain and occupy significant storage space.

Logs & Screenshots

Image

Additional Information

No response

Originally created by @mokieli on GitHub (May 20, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14076 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.10 ### Ollama Version (if applicable) _No response_ ### Operating System Windows11 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior When a file collection is deleted from the knowledge base via the WebUI, all associated files — including both the original text files in the uploads folder and the parsed data in the vector_db folder — should be completely removed from the Docker volume. Additionally, executing "Reset Upload Directory," "Reset Vector Storage/Knowledge," and "Rebuild Knowledge Base Vectors" should fully clear any residual vector data and free up storage space. ### Actual Behavior After deleting a file collection from the knowledge base via the WebUI, the uploads folder and vector_db folder inside the Docker volume still retain the original text files imported into the knowledge base and the parsed data files. Moreover, the parsed data files in vector_db take up a significant amount of storage space. Performing 'Reset Upload Directory', 'Reset Vector Storage/Knowledge', and 'Rebuild Knowledge Base Vectors' in the Admin Settings under the Document section does not remove the residual data in vector_db; only the contents of the uploads folder are cleared. ### Steps to Reproduce 1. Launch Open-WebUI and navigate to the Knowledge Base section. 2. Create a new knowledge base or use an existing one. 3. Upload a text file to the knowledge base via the WebUI. 4. Wait for the file to be fully parsed and processed. 5. Delete the uploaded file from the knowledge base through the WebUI interface. 6. Access the Docker volume associated with Open-WebUI. 7. Navigate to the `uploads` folder within the volume and verify that the original file has been removed. 8. Navigate to the `vector_db` folder and observe that the parsed vector data files related to the deleted file still remain and occupy significant storage space. ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/1a18b22e-c006-4d65-8329-132e2606c57d) ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-25 05:35:38 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#136858