fix: mount dev compose volume to writable path#134
Merged
chaptersix merged 2 commits intomainfrom Mar 10, 2026
Merged
Conversation
The SQLite DB file could not be created at /data because the volume is root-owned but the container runs as the temporal user. Mount to /home/temporal instead, which is already owned by the temporal user.
Adds a compose-dev-test job that validates the dev compose file starts correctly and Temporal is functional. This would have caught the SQLite permission issue.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
docker-compose-dev.ymlcaused by the volume mounting to/data(root-owned) while the container runs as thetemporaluser/home/temporalinstead, which is already owned by thetemporaluserdocker-compose-dev.ymlto catch this class of issueTest plan
docker compose -f docker-compose-dev.yml upstarts successfully