Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4343] [BUG]: Settings Are Wiped on Container Recreation After Version Update or Config Change #2767

New Issue
Closed
opened 2026-02-22 18:31:09 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:31:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @Wetoshkin on GitHub (Aug 31, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4343

How are you running AnythingLLM?

Docker (local)

What happened?

Hello AnythingLLM Team,

First off, thank you for creating such a powerful and useful application. I'm writing to report a critical issue regarding data persistence that makes updating the application very difficult.

The Problem
The global settings under the "AI Providers" section of the admin panel are completely wiped and reset to their default values whenever the Docker container is recreated after an image update or a simple change in the docker-compose.yml file.

This happens even though the storage volume is correctly mounted. All user-specific data, such as chat history and workspaces, is correctly preserved. The issue is specific to the administrative settings shown in the screenshot below (LLM Preference, Vector Database, Embedding Settings, Text Splitting, Voice/Speech, and Transcription Model).

It seems the application forcefully re-initializes the configuration part of the anythingllm.db database on startup if it detects a version or configuration change, rather than migrating the existing settings.

My Docker Compose Setup:

services:
  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    ports:
      - "3001:3001"
    volumes:
      - ./vpn.conf:/gluetun/custom.ovpn:ro
    environment:
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=openvpn
      - OPENVPN_CUSTOM_CONFIG=/gluetun/custom.ovpn
      - TZ=Asia/Tomsk
    restart: unless-stopped

  anythingllm:
    image: mintplexlabs/anythingllm
    container_name: anythingllm
    depends_on:
      - gluetun
    network_mode: "service:gluetun"
    cap_add:
      - SYS_ADMIN
    volumes:
      - ./storage:/app/server/storage
      - ./hotdir:/app/collector/hotdir
    environment:
      - "LANCEDB_API_KEY=***"
      - "STORAGE_DIR=/app/server/storage"
      - "JWT_SECRET=***"
      - "ENABLE_MULTI_USER=true"
    restart: unless-stopped

Steps to Reproduce
Start the application using image: mintplexlabs/anythingllm:v1.8.4.

Configure all necessary settings in the "AI Providers" section of the web UI.

Stop the containers with docker compose down.

Change the image tag to mintplexlabs/anythingllm:latest to simulate an update.

Run docker compose up -d --force-recreate.

Open the web UI and navigate to the Admin Settings.

Result:
All chat history and workspaces are still present. However, all settings under "AI Providers" have been reset to their defaults, making the application non-functional until they are re-configured. The initial setup screen is not shown.

Expected Behavior
Global application settings under "AI Providers" should be preserved during version upgrades and container recreations.

Related Issue
As a side note, the Docker image for the GitHub release v1.8.5 appears to be missing from Docker Hub. The latest tag still points to v1.8.4 even though the v1.8.5 release was weeks ago. This lack of a tagged update path is what led to the discovery of the settings-wipe issue.

Thank you for your time and for looking into this.

Are there known steps to reproduce?

No response

Originally created by @Wetoshkin on GitHub (Aug 31, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4343 ### How are you running AnythingLLM? Docker (local) ### What happened? Hello AnythingLLM Team, First off, thank you for creating such a powerful and useful application. I'm writing to report a critical issue regarding data persistence that makes updating the application very difficult. **The Problem** The global settings under the "AI Providers" section of the admin panel are completely wiped and reset to their default values whenever the Docker container is recreated after an image update or a simple change in the docker-compose.yml file. This happens even though the storage volume is correctly mounted. All user-specific data, such as chat history and workspaces, is correctly preserved. The issue is specific to the administrative settings shown in the screenshot below (LLM Preference, Vector Database, Embedding Settings, Text Splitting, Voice/Speech, and Transcription Model). It seems the application forcefully re-initializes the configuration part of the anythingllm.db database on startup if it detects a version or configuration change, rather than migrating the existing settings. **My Docker Compose Setup:** ``` services: gluetun: image: qmcgaw/gluetun container_name: gluetun cap_add: - NET_ADMIN ports: - "3001:3001" volumes: - ./vpn.conf:/gluetun/custom.ovpn:ro environment: - VPN_SERVICE_PROVIDER=custom - VPN_TYPE=openvpn - OPENVPN_CUSTOM_CONFIG=/gluetun/custom.ovpn - TZ=Asia/Tomsk restart: unless-stopped anythingllm: image: mintplexlabs/anythingllm container_name: anythingllm depends_on: - gluetun network_mode: "service:gluetun" cap_add: - SYS_ADMIN volumes: - ./storage:/app/server/storage - ./hotdir:/app/collector/hotdir environment: - "LANCEDB_API_KEY=***" - "STORAGE_DIR=/app/server/storage" - "JWT_SECRET=***" - "ENABLE_MULTI_USER=true" restart: unless-stopped ``` **Steps to Reproduce** Start the application using image: mintplexlabs/anythingllm:v1.8.4. Configure all necessary settings in the "AI Providers" section of the web UI. Stop the containers with `docker compose down`. Change the image tag to `mintplexlabs/anythingllm:latest` to simulate an update. Run `docker compose up -d --force-recreate`. Open the web UI and navigate to the Admin Settings. **Result:** All chat history and workspaces are still present. However, all settings under "AI Providers" have been reset to their defaults, making the application non-functional until they are re-configured. The initial setup screen is not shown. **Expected Behavior** Global application settings under "AI Providers" should be preserved during version upgrades and container recreations. **Related Issue** As a side note, the Docker image for the GitHub release v1.8.5 appears to be missing from Docker Hub. The latest tag still points to v1.8.4 even though the v1.8.5 release was weeks ago. This lack of a tagged update path is what led to the discovery of the settings-wipe issue. Thank you for your time and for looking into this. ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:31:09 -05:00
yindo closed this issue 2026-02-22 18:31:10 -05:00
yindo commented 2026-02-22 18:31:10 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Sep 3, 2025):

I see volumes are used, but they are not mapped to a host-level storage, meaning when you delete the container the volumes are gone too.

The quickstart command maps the volumes to host-level storage in a folder in the userspace $HOME to prevent this.

As a side note, the Docker image for the GitHub release v1.8.5 appears to be missing from Docker Hub.

https://hub.docker.com/layers/mintplexlabs/anythingllm/1.8.5/images/sha256-f1bde0d4b290220299647afdd0c07a6d4c8f81f021b81b9e48c43aafdf5ba3b7

yeah?

@timothycarambat commented on GitHub (Sep 3, 2025): I see volumes are used, but they are not mapped to a host-level storage, meaning when you delete the container the volumes are gone too. The [quickstart command](https://docs.anythingllm.com/installation-docker/quickstart) maps the volumes to host-level storage in a folder in the userspace $HOME to prevent this. > As a side note, the Docker image for the GitHub release v1.8.5 appears to be missing from Docker Hub. https://hub.docker.com/layers/mintplexlabs/anythingllm/1.8.5/images/sha256-f1bde0d4b290220299647afdd0c07a6d4c8f81f021b81b9e48c43aafdf5ba3b7 yeah?
yindo changed title from [BUG]: Settings Are Wiped on Container Recreation After Version Update or Config Change to [GH-ISSUE #4343] [BUG]: Settings Are Wiped on Container Recreation After Version Update or Config Change 2026-06-05 14:48:26 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2767
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?