Transmission container plus volume management #15
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.
This PR is to add Transmission container, no more included as plugin into OpenMediaVault 5 release, that uses OMV shared folders.
To make sure the folders are shared between OMV5 and Transmission container, a volume is needed as explained in approach #2 here.
For this reason, it's required the management of new "volumes.yml" file into menu.sh, that can be used by any template, to append all the volume's declaration at the end of docker-compose.yml
Thank you of your awesome job, hope you'll enjoy this PR!
This is from: gcgarner#160 Contributor: @gpongelli