Transmission container plus volume management

[gpongelli]

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!

[Slyke]

Hey @gpongelli would you mind fixing the merge conflict? we just put each of the menu items on seperate lines so that merge conflicts in the future are easier to manage. I'm also about to merge #11 in. Would you prefer to use qbittorrent, or you think Transmission also has a place?

[gpongelli]

Good idea to put menu items on separate lines, fixed using web client.
I've already used Transmission, alone with this container and actually I'm using it together with openvpn .

I think that all three containers can cohabit, so anyone can choose which it's best.

[Slyke]

Awesome, this PR is next on my list for testing then. Just finishing up testing #19 and will start on this one.

[Slyke]

For now, can you make these actual paths?

/home/${USER}/IOTstack/.volumes/transmission/downloads

Or something.

Otherwise it causes an error when starting:

Needs to be done for all 3

[gpongelli]

Sure! I put it as a bookmark to be changed after running menu.sh, so anyone can use the absolute path he/she want (e.g. I have them on an external hd).

[Slyke]

This will likely need to be updated in the future once we have yaml merging on. Just letting you know in case it breaks your current setup when that upgrade happens.

[gpongelli]

Ok no problem. I did in this way to have the code written in a similar fashion to the original

[Slyke]

Hey @gpongelli I just tried running this on a fresh installation and getting the following error:

Status: Downloaded newer image for linuxserver/transmission:latest
Creating transmission ... error

ERROR: for transmission  Cannot create container for service transmission: failed to mount local volume: mount /home/pi/IOTstack/.volumes/transmission/config:/var/lib/docker/volumes/iotstack_transm_config_volume/_data, flags: 0x1000: no such file or directory

ERROR: for transmission  Cannot create container for service transmission: failed to mount local volume: mount /home/pi/IOTstack/.volumes/transmission/config:/var/lib/docker/volumes/iotstack_transm_config_volume/_data, flags: 0x1000: no such file or directory
ERROR: Encountered errors while bringing up the project.

Could you update the installation steps so that it create the required files and folders? It should be able to run once installing it, with the ability for the user to change the docker image if they choose to. I would help, but I can't push changes to commits from forked repos.

[gpongelli]

Yes, unlike usual volume management, those folder must exist before running docker-compose.

Could you update the installation steps so that it create the required files and folders? It should be able to run once installing it, with the ability for the user to change the docker image if they choose to. I would help, but I can't push changes to commits from forked repos.

I've no idea on how to do that, what do you mean with "installation steps" ?
I've invited you as collaborator on my fork so you can push directly the fix on my branch.

[Slyke]

Just pushed the changes to your github and approved the PR here. Transmission should now run without errors with the named volumes, and have the directories automatically created for them at build time without any config changes.

[Slyke]

@gpongelli PR #38 may break your current system. There's details in the PR on how to mitigate.