[GH-ISSUE #2975] [BUG]: Telemetry settings not persistent #1901

Closed
opened 2026-02-22 18:27:08 -05:00 by yindo · 1 comment
Owner

Originally created by @pmffromspace on GitHub (Jan 15, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2975

How are you running AnythingLLM?

Docker (local)

What happened?

I disabled telemetry, after recreation of container its enabled again. I think the telemetry settings should be persistent.
(/settings/privacy)

Are there known steps to reproduce?

No response

Originally created by @pmffromspace on GitHub (Jan 15, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2975 ### How are you running AnythingLLM? Docker (local) ### What happened? I disabled telemetry, after recreation of container its enabled again. I think the telemetry settings should be persistent. (/settings/privacy) ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:27:08 -05:00
yindo closed this issue 2026-02-22 18:27:08 -05:00
Author
Owner

@timothycarambat commented on GitHub (Jan 15, 2025):

Are you binding the volume externally?

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

-v ${STORAGE_LOCATION}/.env:/app/server/.env binds a host FS .env to the containers - persisting between container creations. Since the Telem ENV is stored in there, it would persist. If you are not running the above command, you are basically blowing away your entire config every container start/stop. You would also never be able to update the image since the volume would be container-bound.

@timothycarambat commented on GitHub (Jan 15, 2025): Are you binding the volume externally? ``` 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 ``` `-v ${STORAGE_LOCATION}/.env:/app/server/.env` binds a host FS `.env` to the containers - persisting between container creations. Since the Telem ENV is stored in there, it would persist. If you are not running the above command, you are basically blowing away your entire config every container start/stop. You would also never be able to update the image since the volume would be container-bound.
yindo changed title from [BUG]: Telemetry settings not persistent to [GH-ISSUE #2975] [BUG]: Telemetry settings not persistent 2026-06-05 14:43:20 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1901