Fix: Add init container for volume permission management in docker-compose.yml #7305
+8
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dosubot
bot
added
size:XS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
I noticed that the current configuration was causing files to be stored at
/app/app/langflowinstead of the mounted volume path/app/langflow. This created a risk of data loss as files weren't being properly saved to the persistent volume.Changes Made
LANGFLOW_CONFIG_DIRenvironment variable to point to/app/langflowto ensure data is stored in the correct mounted volume location.chown-volumeconfiguration to address permission issues, as the langflow container runs with uid 1000 and was unable to write to the volume with the previous setup.I'd appreciate your feedback on this approach. Please let me know if you have any concerns or suggestions for improvement.