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

[PR #714] [MERGED] Fix Docker container exit issue by changing ownership #3469

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

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/714
Author: @cloud-ray
Created: 2/13/2024
Status: ✅ Merged
Merged: 2/13/2024
Merged by: @timothycarambat

Base: master ← Head: gcp-fix-docker-exit-issue

📝 Commits (1)

  • 1c2306c Fix Docker container exit issue by changing ownership

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 cloud-deployments/gcp/deployment/gcp_deploy_anything_llm.yaml (+1 -0)

📄 Description

Pull Request Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

Relevant Issues

resolves #710
resolves #702
resolves #695

What is in this change?

This PR addresses an issue where the Docker container would start but then exit due to the error "unable to open database file: ../storage/anythingllm.db". The fix involves modifying the gcp_deploy_anything_llm.yaml file to change the ownership of the /home/anythingllm directory using the command: sudo chown -R ubuntu:ubuntu /home/anythingllm. This solution was preferred over changing the Docker runner from using a user and running as root.

Additional Information

This change was discussed with @timothycarambat and agreed upon as the preferred solution. It also addresses a similar issue (#702).

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/714 **Author:** [@cloud-ray](https://github.com/cloud-ray) **Created:** 2/13/2024 **Status:** ✅ Merged **Merged:** 2/13/2024 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `gcp-fix-docker-exit-issue` --- ### 📝 Commits (1) - [`1c2306c`](https://github.com/Mintplex-Labs/anything-llm/commit/1c2306c36173ca4da1b59b0c1ff8a7692ce9c134) Fix Docker container exit issue by changing ownership ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `cloud-deployments/gcp/deployment/gcp_deploy_anything_llm.yaml` (+1 -0) </details> ### 📄 Description ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [ ] ✨ feat - [x] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### Relevant Issues <!-- Use "resolves #xxx" to auto resolve on merge. Otherwise, please use "connect #xxx" --> resolves #710 resolves #702 resolves #695 ### What is in this change? This PR addresses an issue where the Docker container would start but then exit due to the error "unable to open database file: ../storage/anythingllm.db". The fix involves modifying the `gcp_deploy_anything_llm.yaml` file to change the ownership of the /home/anythingllm directory using the command: sudo chown -R ubuntu:ubuntu /home/anythingllm. This solution was preferred over changing the Docker runner from using a user and running as root. ### Additional Information This change was discussed with @timothycarambat and agreed upon as the preferred solution. It also addresses a similar issue (#702). ### Developer Validations <!-- All of the applicable items should be checked. --> - [ ] I ran `yarn lint` from the root of the repo & committed changes - [ ] Relevant documentation has been updated - [x] I have tested my code functionality - [x] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:33:51 -05:00
yindo closed this issue 2026-02-22 18:33:51 -05:00
yindo changed title from [PR #714] Fix Docker container exit issue by changing ownership to [PR #714] [MERGED] Fix Docker container exit issue by changing ownership 2026-06-05 15:13:34 -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 pull-request
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#3469
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?