Repository navigation
docs: clarify Docker data persistence - #26
Open
dajiaohuang wants to merge 1 commit into
Open
dajiaohuang wants to merge 1 commit into
dajiaohuang wants to merge 1 commit into
Conversation
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
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.
The README said settings are lost on a container restart and torrent data is always ephemeral, but the application writes both under
/appand the Compose example bind-mounts./torrent-datato the host. Clarify that the container writable layer survives process restarts, is lost on container removal/recreation, and the torrent-data bind mount persists files on the host.Validation: verified the storage path (
storage.NewFile(./torrent-data)), DockerWORKDIR /app, and purge/teardown behavior by source inspection.git diff --checkpasses. No app/container or media runtime was used.