Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Torrents don't resume on docker container stop/start #23

Closed
dougnukem opened this issue Aug 13, 2015 · 2 comments
Closed

Torrents don't resume on docker container stop/start #23

dougnukem opened this issue Aug 13, 2015 · 2 comments

Comments

@dougnukem
Copy link
Contributor

Torrents aren't resuming when the docker container is stopped/started, even though the /data/incomplet and /data/watch has *.torrent.added and *.part files.

I think there must be some other Transmission configuration or directory that is managing this state that needs to be located in the /data or /config volumes so it can be restored on docker container restart.

@dougnukem
Copy link
Contributor Author

It looks like the /etc/transmission-daemon file contains some important state https://trac.transmissionbt.com/wiki/ConfigFiles

  • resume/ - This subfolder holds .resume files that hold information about a particular torrent, such as which parts have been downloaded, the folder the downloaded data was stored in, and so on. These follow an identical naming scheme to the files in the torrents subfolder.
  • torrents/ - This subfolder holds the .torrent files that have been added to Transmission. The files in this folder are named with a combination of the torrent's name (to make it human-readable) and a portion of the torrent's SHA1 hash (to avoid filename collisions from similarly-named torrents).

dougnukem added a commit to dougnukem/docker-transmission-openvpn that referenced this issue Aug 13, 2015
@haugene
Copy link
Owner

haugene commented Aug 15, 2015

Fix merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants