Fix Docker container exit issue by changing ownership #714
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Type
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.yamlfile 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
yarn lintfrom the root of the repo & committed changes