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

[GH-ISSUE #4302] [BUG]: Emedding gets reset after each container restart #2734

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

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

How are you running AnythingLLM?

Docker (remote machine)

What happened?

After a fresh docker installation on Ubuntu 24 using the 1st method from the docker howto, on the /settings/embedding-preference page the Embedding Provider was initially set to Ollama. If I set it to anything else, it gets reset back to Ollama after every container restart (or crash).

I add some documents, it crashes, I try to add more, it says it can't Ollama isn't configured, and if I wanna change the embedder that will wipe out the documents already added.

Are there known steps to reproduce?

fresh docker install + onboarding done
docker stop container-id
docker start container-id

Originally created by @hiiamboris on GitHub (Aug 17, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4302 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? After a fresh docker installation on Ubuntu 24 using the 1st method from the [docker howto](https://github.com/Mintplex-Labs/anything-llm/blob/master/docker/HOW_TO_USE_DOCKER.md#recommend-way-to-run-dockerized-anythingllm), on the `/settings/embedding-preference` page the Embedding Provider was initially set to Ollama. If I set it to anything else, it gets reset back to Ollama after every container restart (or crash). I add some documents, it crashes, I try to add more, it says it can't Ollama isn't configured, and if I wanna change the embedder that will wipe out the documents already added. ### Are there known steps to reproduce? fresh docker install + onboarding done docker stop container-id docker start container-id
yindo added the possible bug label 2026-02-22 18:31:00 -05:00
yindo closed this issue 2026-02-22 18:31:00 -05:00
yindo commented 2026-02-22 18:31:01 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Aug 17, 2025):

and if I wanna change the embedder that will wipe out the documents already added.

Sounds like your documents never actually embedded since you claim it crashed, so there would be nothing to embed since nothing was ever output. I know from the previous post you are using a larger embedder model with an under-resourced VM. That is the core of all of your issues. Use the default embedder or get a better VM provisioned

@timothycarambat commented on GitHub (Aug 17, 2025): > and if I wanna change the embedder that will wipe out the documents already added. Sounds like your documents never actually embedded since you claim it crashed, so there would be nothing to embed since nothing was ever output. I know from the previous post you are using a larger embedder model with an under-resourced VM. That is the core of all of your issues. Use the default embedder or get a better VM provisioned
yindo commented 2026-02-22 18:31:01 -05:00
Author
Owner
Copy Link
Copy Source

@hiiamboris commented on GitHub (Aug 18, 2025):

Looks like you don't care about the quality of this project if you dismiss issues so easily. It is clear from the description that this issue is not about the embedding failure, but about a provider reset. For which I even gave you a simple command to reproduce (though reboot is another one). It doesn't matter what embedder I choose and whether I have successfully embedded any documents or not. It always ends up using Ollama.

@hiiamboris commented on GitHub (Aug 18, 2025): Looks like you don't care about the quality of this project if you dismiss issues so easily. It is clear from the description that this issue is not about the embedding failure, but about a provider reset. For which I even gave you a simple command to reproduce (though `reboot` is another one). It doesn't matter what embedder I choose and whether I have successfully embedded any documents or not. It always ends up using Ollama.
yindo changed title from [BUG]: Emedding gets reset after each container restart to [GH-ISSUE #4302] [BUG]: Emedding gets reset after each container restart 2026-06-05 14:48:15 -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#2734
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?