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 #5710] [POSSIBLE BUG]: ENV File getting reset? #5250

New Issue
Closed
opened 2026-06-05 14:52:55 -04:00 by yindo · 5 comments
yindo commented 2026-06-05 14:52:55 -04:00
Owner
Copy Link
Copy Source

Originally created by @ohromeo on GitHub (May 27, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5710

How are you running AnythingLLM?

Docker (local)

What happened?

Hi,
just noticing my .env file is being reset to a default of sorts??, i did an upgrade yesterday and the .env was reset.

it had this at the top:

Auto-dump ENV from system call on 07:10:31 GMT+0000 (Coordinated Universal Time)

not sure if there's something enabled, all my data intact so i belive the upgrade isn't wiping the system..
the startup command is from the docs:

docker stop allm && docker rm allm export STORAGE_LOCATION="$HOME/anythingllm" && \ mkdir -p "$STORAGE_LOCATION" && \ touch "$STORAGE_LOCATION/.env" && \ docker run -d \ --name allm \ -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" \ --restart unless-stopped \ mintplexlabs/anythingllm:latest

not sure what's going on

thanks

Are there known steps to reproduce?

not sure, perform an upgrade

LLM Provider & Model (if applicable)

n/a

Embedder Provider & Model (if applicable)

n/a

Originally created by @ohromeo on GitHub (May 27, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5710 ### How are you running AnythingLLM? Docker (local) ### What happened? Hi, just noticing my .env file is being reset to a default of sorts??, i did an upgrade yesterday and the .env was reset. it had this at the top: # Auto-dump ENV from system call on 07:10:31 GMT+0000 (Coordinated Universal Time) not sure if there's something enabled, all my data intact so i belive the upgrade isn't wiping the system.. the startup command is from the docs: `docker stop allm && docker rm allm export STORAGE_LOCATION="$HOME/anythingllm" && \ mkdir -p "$STORAGE_LOCATION" && \ touch "$STORAGE_LOCATION/.env" && \ docker run -d \ --name allm \ -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" \ --restart unless-stopped \ mintplexlabs/anythingllm:latest ` not sure what's going on thanks ### Are there known steps to reproduce? not sure, perform an upgrade ### LLM Provider & Model (if applicable) n/a ### Embedder Provider & Model (if applicable) n/a
yindo added the possible bug label 2026-06-05 14:52:55 -04:00
yindo closed this issue 2026-06-05 14:52:55 -04:00
yindo commented 2026-06-05 14:52:56 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 27, 2026):

What specifically was "reset" here? The file will always be updated - so that header is always written even if you didnt change anything.

<!-- gh-comment-id:4556102924 --> @timothycarambat commented on GitHub (May 27, 2026): What specifically was "reset" here? The file will always be updated - so that header is always written even if you didnt change anything.
yindo commented 2026-06-05 14:52:56 -04:00
Author
Owner
Copy Link
Copy Source

@ohromeo commented on GitHub (May 27, 2026):

Hi Tim,

i added these items:

UID='1000'
GID='1000'
DISABLE_SWAGGER_DOCS="true"
AGENT_AUTO_APPROVED_SKILLS=""
COMMUNITY_HUB_BUNDLE_DOWNLOADS_ENABLED="1"
REQUEST_TIMEOUT=900000
OLLAMA_LOAD_TIMEOUT=900000

as i write this... the .env is missing the items above, as well as some items i copied from the git example env file (they wrere #, just for reference)

i've reverted back to 1.12.1 to test this and the other embedding issue

<!-- gh-comment-id:4557187599 --> @ohromeo commented on GitHub (May 27, 2026): Hi Tim, i added these items: UID='1000' GID='1000' DISABLE_SWAGGER_DOCS="true" AGENT_AUTO_APPROVED_SKILLS="<all>" COMMUNITY_HUB_BUNDLE_DOWNLOADS_ENABLED="1" REQUEST_TIMEOUT=900000 OLLAMA_LOAD_TIMEOUT=900000 as i write this... the .env is missing the items above, as well as some items i copied from the git example env file (they wrere #, just for reference) i've reverted back to 1.12.1 to test this and the other embedding issue
yindo commented 2026-06-05 14:52:56 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 27, 2026):

https://github.com/Mintplex-Labs/anything-llm/blob/bee224171c1ea2236643b2c6f6622a0a63b6b7b3/server/utils/helpers/updateENV.js#L1312-L1378

These are the only special ENVs which are not settable from the UI that would get pruned? Like UID, GID, REQUEST_TIMEOUT, OLLAMA_LOAD_TIMEOUT are all envs for other systems, not AnythingLLM

Like UID,GID should be passed in as docker args, OLLAMA_LOAD_TIMEOUT should be passed in on ollama run. IDK about REQUEST_TIMEOUT - that isnt something we have universal support for so not sure where that one comes from

<!-- gh-comment-id:4557574347 --> @timothycarambat commented on GitHub (May 27, 2026): https://github.com/Mintplex-Labs/anything-llm/blob/bee224171c1ea2236643b2c6f6622a0a63b6b7b3/server/utils/helpers/updateENV.js#L1312-L1378 These are the only special ENVs which are not settable from the UI that would get pruned? Like UID, GID, REQUEST_TIMEOUT, OLLAMA_LOAD_TIMEOUT are all envs for other systems, not AnythingLLM Like UID,GID should be passed in as docker args, OLLAMA_LOAD_TIMEOUT should be passed in on ollama run. IDK about REQUEST_TIMEOUT - that isnt something we have universal support for so not sure where that one comes from
yindo commented 2026-06-05 14:52:56 -04:00
Author
Owner
Copy Link
Copy Source

@ohromeo commented on GitHub (May 27, 2026):

Thanks for that, i grabbed them from.the docs and probably searched others.

Is.possible not to remove this one, or where would the appropriate location be?. I'm running linux/docker 1.13.0

DISABLE_SWAGGER_DOCS="true"

Thanks!

<!-- gh-comment-id:4560411839 --> @ohromeo commented on GitHub (May 27, 2026): Thanks for that, i grabbed them from.the docs and probably searched others. Is.possible not to remove this one, or where would the appropriate location be?. I'm running linux/docker 1.13.0 DISABLE_SWAGGER_DOCS="true" Thanks!
yindo commented 2026-06-05 14:52:56 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 27, 2026):

Ah, that one it not in the list (it is a very very old ENV) - I can add it to the list right now so it stops getting popped off

<!-- gh-comment-id:4560623700 --> @timothycarambat commented on GitHub (May 27, 2026): Ah, that one it not in the list (it is a very very old ENV) - I can add it to the list right now so it stops getting popped off
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#5250
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?