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 #710] [BUG]: GCP Cloud Deployment YAML #411

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

Originally created by @cloud-ray on GitHub (Feb 10, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/710

How are you running AnythingLLM?

Docker (remote machine)

What happened?

Hello. I've come across an issue running the 'gcp_deploy_anything_llm.yaml' as is (on the Ubuntu instance).

The Docker container will start, but exit due to the issue "unable to open database file: ../storage/anythingllm.db".

The workaround I have found is running the command: sudo chown -R ubuntu:ubuntu /home/anythingllm

With this, the database creates properly. I've uploaded the workaround line to the yaml in this repo.

I also wrote about my experience with AnythingLLM in this article: Craft Your Own AI-Powered Knowledge Base: Wordpress + Ollama + AnythingLLM

I'm not 100% sure this is the recommended way to fix it, which is why I did not submit a pull request. I'd be happy if you'd prefer.

Hope this helps!

1-docker-exit 2-chown-folder 3-rerun 4-db-created

Are there known steps to reproduce?

No response

Originally created by @cloud-ray on GitHub (Feb 10, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/710 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? Hello. I've come across an issue running the 'gcp_deploy_anything_llm.yaml' as is (on the Ubuntu instance). The Docker container will start, but exit due to the issue "unable to open database file: ../storage/anythingllm.db". The workaround I have found is running the command: sudo chown -R ubuntu:ubuntu /home/anythingllm With this, the database creates properly. I've uploaded the workaround line to the yaml [in this repo.](https://github.com/cloud-ray/anything-llm-deployment) I also wrote about my experience with AnythingLLM in this article: [Craft Your Own AI-Powered Knowledge Base: Wordpress + Ollama + AnythingLLM](https://cloudray.medium.com/craft-your-own-ai-powered-knowledge-base-wordpress-ollama-anythingllm-04dc4260dd37) I'm not 100% sure this is the recommended way to fix it, which is why I did not submit a pull request. I'd be happy if you'd prefer. Hope this helps! <img width="874" alt="1-docker-exit" src="https://github.com/Mintplex-Labs/anything-llm/assets/120739995/c382b690-8218-4082-936c-89214bb7a262"> <img width="641" alt="2-chown-folder" src="https://github.com/Mintplex-Labs/anything-llm/assets/120739995/bf0b9b94-2464-44a0-ad8b-90205b2ca035"> <img width="897" alt="3-rerun" src="https://github.com/Mintplex-Labs/anything-llm/assets/120739995/2de58a82-8bb9-41b6-8f03-a332dcbada51"> <img width="688" alt="4-db-created" src="https://github.com/Mintplex-Labs/anything-llm/assets/120739995/cbac396c-0e20-44a0-a18a-4806e8093d8c"> ### Are there known steps to reproduce? _No response_
yindo added the documentationDocker labels 2026-02-22 18:19:21 -05:00
yindo closed this issue 2026-02-22 18:19:22 -05:00
yindo commented 2026-02-22 18:19:22 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 10, 2024):

Hey @cloud-ray, this is a great write up. In my opinion I would be happy to merge a PR with that chmod fix. My primary reasoning is that the risk level of that folder running is quite low.

Alternatively, the alternative is changing the docker runner from using a user and running as root, which I'm less comfortable with.

We saw a similar issue with https://github.com/Mintplex-Labs/anything-llm/issues/702 and if you make that PR it would close two issues at the same time.

These templates are community-maintained anyway. That being said let me know if you would like to do the PR or if you would like us to handle it. Either way, I appreciate the write up and report on this.

@timothycarambat commented on GitHub (Feb 10, 2024): Hey @cloud-ray, this is a great write up. In my opinion I would be happy to merge a PR with that `chmod` fix. My primary reasoning is that the risk level of that folder running is quite low. Alternatively, the alternative is changing the docker runner from using a user and running as root, which I'm less comfortable with. We saw a similar issue with https://github.com/Mintplex-Labs/anything-llm/issues/702 and if you make that PR it would close two issues at the same time. These templates are community-maintained anyway. That being said let me know if you would like to do the PR or if you would like us to handle it. Either way, I appreciate the write up and report on this.
yindo commented 2026-02-22 18:19:22 -05:00
Author
Owner
Copy Link
Copy Source

@cloud-ray commented on GitHub (Feb 11, 2024):

Hello @timothycarambat, thank you for your response. I'll submit the PR. #702 suggested chmod and I used chown. Do you have a preference?

@cloud-ray commented on GitHub (Feb 11, 2024): Hello @timothycarambat, thank you for your response. I'll submit the PR. #702 suggested _chmod_ and I used _chown_. Do you have a preference?
yindo commented 2026-02-22 18:19:22 -05:00
Author
Owner
Copy Link
Copy Source

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

chown makes more sense since we need to change the user ownership, not really the permissions since the entire system does not need access, only the user

@timothycarambat commented on GitHub (Feb 12, 2024): `chown` makes more sense since we need to change the user ownership, not really the permissions since the entire system does not need access, only the user
yindo commented 2026-02-22 18:19:22 -05:00
Author
Owner
Copy Link
Copy Source

@cloud-ray commented on GitHub (Feb 16, 2024):

Thanks again for your help @timothycarambat!

@cloud-ray commented on GitHub (Feb 16, 2024): Thanks again for your help @timothycarambat!
yindo changed title from [BUG]: GCP Cloud Deployment YAML to [GH-ISSUE #710] [BUG]: GCP Cloud Deployment YAML 2026-06-05 14:35:09 -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 Docker 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#411
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?