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 #1660] How can I upgrade "anythingllm" built with docker? #1082

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

Originally created by @mingLvft on GitHub (Jun 11, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1660

How can I upgrade "anythingllm" built with docker?

Originally created by @mingLvft on GitHub (Jun 11, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1660 How can I upgrade "anythingllm" built with docker?
yindo added the documentation label 2026-02-22 18:23:02 -05:00
yindo closed this issue 2026-02-22 18:23:02 -05:00
yindo commented 2026-02-22 18:23:02 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 12, 2024):

https://docs.useanything.com/update#updating-on-docker

@timothycarambat commented on GitHub (Jun 12, 2024): https://docs.useanything.com/update#updating-on-docker
yindo commented 2026-02-22 18:23:03 -05:00
Author
Owner
Copy Link
Copy Source

@gcleaves commented on GitHub (Dec 3, 2024):

@timothycarambat the link is no longer available. Upgrade instructions would be great. Last time I tried it I nuked the installation and had to build everything again from scratch.

Usually I just update the image version in the compose file and do docker compose up -d to upgrade other systems. But it failed for me.

@gcleaves commented on GitHub (Dec 3, 2024): @timothycarambat the link is no longer available. Upgrade instructions would be great. Last time I tried it I nuked the installation and had to build everything again from scratch. Usually I just update the image version in the compose file and do `docker compose up -d` to upgrade other systems. But it failed for me.
yindo commented 2026-02-22 18:23:03 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Dec 4, 2024):

You would just run the same command to start after a docker pull
https://docs.anythingllm.com/installation-docker/local-docker

Since the volume for the storage is on the host, it will persist between container destroys and image pulls

@timothycarambat commented on GitHub (Dec 4, 2024): You would just run the same command to start after a `docker pull` https://docs.anythingllm.com/installation-docker/local-docker Since the volume for the storage is on the host, it will persist between container destroys and image pulls
yindo commented 2026-02-22 18:23:03 -05:00
Author
Owner
Copy Link
Copy Source

@gcleaves commented on GitHub (Dec 5, 2024):

Unfortunately when I do that, the new instance starts giving all sorts of front end javascript errors. It's now happened to me twice. It makes no sense. I wonder if it has something to do with being behind an NGINX reverse proxy for TLS termination that somehow confuses the front end after an upgrade (even if the front end and back end get updated simultaneously.)

I'll need to make a video to prove I'm not crazy ;)

@gcleaves commented on GitHub (Dec 5, 2024): Unfortunately when I do that, the new instance starts giving all sorts of front end javascript errors. It's now happened to me twice. It makes no sense. I wonder if it has something to do with being behind an NGINX reverse proxy for TLS termination that somehow confuses the front end after an upgrade (even if the front end and back end get updated simultaneously.) I'll need to make a video to prove I'm not crazy ;)
yindo commented 2026-02-22 18:23:03 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Dec 5, 2024):

the new instance starts giving all sorts of front end javascript errors

Can you post some? Should be an easy solve. Reverse proxy on NGINX is pretty normal practice and we do it internally for some instances so I know for sure it works. Sharing your site NGINX config could also show where things are going awry

@timothycarambat commented on GitHub (Dec 5, 2024): > the new instance starts giving all sorts of front end javascript errors Can you post some? Should be an easy solve. Reverse proxy on NGINX is pretty normal practice and we do it internally for some instances so I know for sure it works. Sharing your site NGINX config could also show where things are going awry
yindo commented 2026-02-22 18:23:03 -05:00
Author
Owner
Copy Link
Copy Source

@gcleaves commented on GitHub (Dec 5, 2024):

I disabled an asset caching setting on the reverse proxy and the problem seems to have gone away.

@gcleaves commented on GitHub (Dec 5, 2024): I disabled an asset caching setting on the reverse proxy and the problem seems to have gone away.
yindo changed title from How can I upgrade "anythingllm" built with docker? to [GH-ISSUE #1660] How can I upgrade "anythingllm" built with docker? 2026-06-05 14:38:53 -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 documentation
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#1082
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?