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 #2497] [BUG]: Unable to upload file to the docker version #1617

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

Originally created by @petrusali on GitHub (Oct 18, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2497

How are you running AnythingLLM?

Docker (remote machine)

What happened?

image I tried to upload any .csv & .pdf files but always got error. And on some files, has never ending upload process. I've waited for up to 30 mins for files around 10MB size.

The problem happen after upgrading to the latest version.

Are there known steps to reproduce?

No response

Originally created by @petrusali on GitHub (Oct 18, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2497 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? <img width="328" alt="image" src="https://github.com/user-attachments/assets/ff06e4cc-bdfe-4a39-8559-1c21c0d8c6ce"> I tried to upload any .csv & .pdf files but always got error. And on some files, has never ending upload process. I've waited for up to 30 mins for files around 10MB size. The problem happen after upgrading to the latest version. ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:25:41 -05:00
yindo closed this issue 2026-02-22 18:25:41 -05:00
yindo commented 2026-02-22 18:25:42 -05:00
Author
Owner
Copy Link
Copy Source

@petrusali commented on GitHub (Oct 18, 2024):

I resolved the issue by repulling the latest image

But the long upload time with seems still there
image
image

@petrusali commented on GitHub (Oct 18, 2024): I resolved the issue by repulling the latest image But the long upload time with seems still there <img width="359" alt="image" src="https://github.com/user-attachments/assets/fde38b8a-46a3-40e7-bcfa-26040cba254b"> <img width="337" alt="image" src="https://github.com/user-attachments/assets/9e89f5ef-d23c-4d2b-9d9f-53e5e2715711">
yindo commented 2026-02-22 18:25:42 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 18, 2024):

You need to run the docker container with the appropriate command:
https://github.com/Mintplex-Labs/anything-llm/blob/master/docker/HOW_TO_USE_DOCKER.md#recommend-way-to-run-dockerized-anythingllm

export STORAGE_LOCATION=$HOME/anythingllm && \
mkdir -p $STORAGE_LOCATION && \
touch "$STORAGE_LOCATION/.env" && \
docker run -d -p 3001:3001 \
--cap-add SYS_ADMIN \
-v ${STORAGE_LOCATION}:/app/server/storage \
-v ${STORAGE_LOCATION}/.env:/app/server/.env \
-e STORAGE_DIR="/app/server/storage" \
mintplexlabs/anythingllm

^ handles storage and web-scraping perms

@timothycarambat commented on GitHub (Oct 18, 2024): You need to run the docker container with the appropriate command: https://github.com/Mintplex-Labs/anything-llm/blob/master/docker/HOW_TO_USE_DOCKER.md#recommend-way-to-run-dockerized-anythingllm ``` export STORAGE_LOCATION=$HOME/anythingllm && \ mkdir -p $STORAGE_LOCATION && \ touch "$STORAGE_LOCATION/.env" && \ docker run -d -p 3001:3001 \ --cap-add SYS_ADMIN \ -v ${STORAGE_LOCATION}:/app/server/storage \ -v ${STORAGE_LOCATION}/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ mintplexlabs/anythingllm ``` ^ handles storage and web-scraping perms
yindo commented 2026-02-22 18:25:42 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 18, 2024):

Also i see you said pulling the latest image changes something. I dont think that is exactly the case, but also parsing document at any speed is heavily dependent on the machine/resources Docker can use on the image.

What are the specs for the machine? Using a t3.mico for instance is going to be very very slow parsing any reasonably sized document and is a resource issue, not a software one!

@timothycarambat commented on GitHub (Oct 18, 2024): Also i see you said pulling the latest image changes something. I dont think that is exactly the case, but also parsing document at any speed is heavily dependent on the machine/resources Docker can use on the image. What are the specs for the machine? Using a t3.mico for instance is going to be very very slow parsing any reasonably sized document and is a resource issue, not a software one!
yindo commented 2026-02-22 18:25:42 -05:00
Author
Owner
Copy Link
Copy Source

@petrusali commented on GitHub (Oct 18, 2024):

Hi Timothy, thanks for your feedback. Actually I did exactly the same as instructed and everything is working perfectly without any issues.

After having some test, I find out that when the PDF doc has images in it. The upload process will stuck. Different from the desktop version where when the PDF has images, the embedding process will ignore the images and only embed the text to the DB.

And for the machine spec, I use Standard_B2ps_v2 from Azure. I monitor the usage is very healthy without any indication of overloading the resources (while the upload process stuck, the CPU and memory usage is nearly 0).

Any further help is very welcome. Thank you.

@petrusali commented on GitHub (Oct 18, 2024): Hi Timothy, thanks for your feedback. Actually I did exactly the same as instructed and everything is working perfectly without any issues. After having some test, I find out that when the PDF doc has images in it. The upload process will stuck. Different from the desktop version where when the PDF has images, the embedding process will ignore the images and only embed the text to the DB. And for the machine spec, I use Standard_B2ps_v2 from Azure. I monitor the usage is very healthy without any indication of overloading the resources (while the upload process stuck, the CPU and memory usage is nearly 0). Any further help is very welcome. Thank you.
yindo commented 2026-02-22 18:25:42 -05:00
Author
Owner
Copy Link
Copy Source

@CRYPTO-GENIK commented on GitHub (Nov 7, 2024):

Why does the docker image require SYS_ADMIN "host root" privileges?

@CRYPTO-GENIK commented on GitHub (Nov 7, 2024): Why does the docker image require SYS_ADMIN "host root" privileges?
yindo commented 2026-02-22 18:25:42 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Nov 7, 2024):

@CRYPTO-GENIK Its answered here https://docs.anythingllm.com/installation-docker/local-docker#recommend-way-to-run-dockerized-anythingllm

@timothycarambat commented on GitHub (Nov 7, 2024): @CRYPTO-GENIK Its answered here https://docs.anythingllm.com/installation-docker/local-docker#recommend-way-to-run-dockerized-anythingllm
yindo changed title from [BUG]: Unable to upload file to the docker version to [GH-ISSUE #2497] [BUG]: Unable to upload file to the docker version 2026-06-05 14:41:45 -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#1617
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?