Hey guys. I'm using ruTorrent 0.9.6/0.13.6 in docker, and everything more or less fine, but after I reboot my machine I lose all my torrent from the list. My other settings remain, but the torrent list gets deleted. Anyone has any ideas why is this happening?
ruTorrent list gets deleted after reboot
-
- OMV 5.x
- Nabukodonosor
-
Post all your container volume bind mounts and any ruTorrent settings that have to do with the location that torrents are stored.
Edit:
Post a link to the docker image you are using.
-
I would say that trying to use undocumented container side directories in volume bind mounts might be the reason for your problem.
Also, the documentation for that image is unusually thin.
I suggest trying another image:
-
Post a screenshot from Portainer of the Volumes being used. Not the section where you have them defined. But from the Container details page.
-
Yes that.
You do realize that the container path /data/torrents is not directly accessible from outside the container. It can only be seen via the host side directory named in the bind mount. What is your need for this /data/torrents directory?
-
That is my download directory. I only need ruTorrent to access it. It downloads there and radarr and sonarr monitor when the download is complete to import it.
I guess I just don't get it.
You use the same identical host side path /MainPool/Multimedia/Media/Download twice. Why?
Are you married to RuTorrent or could you consider using another that may fit your use case beter?
-
Because you have to mount that /downloads to something, or else it mounts it to some local folder it makes. You can't go without it. I've tried, trust me. They've told me you have to mount it to something, even if you don't use it. And if you wonder why I use /data/torrents, check this out:
https://trash-guides.info/How-to-setup-for/Docker/
https://wiki.servarr.com/docke…nt-and-well-planned-paths
Did you find anything that could help me to keep my list persistent after reboot?
[/quote]Are you married to RuTorrent or could you consider using another that may fit your use case beter?[/quote]
Trust me, tried them all. I even have qbittorrent installed and stopped. Haven't deleted it yet.
But ruTorrent have many features that I need that others don't. qbittorrent especially, it's a very feature poor client. -
It doesn't matter what a guide tells you to do if it is unsupported by the image you are using.
Here's the deal, OK.
Agreed, you have to volume bind mount the container path /downloads to a host side directory. You have done this. Twice.
You are also trying to use a container path /data/torrents whis is undocumented for the image you have chosen to use, and which you should assume is therefore not supported. Some docker images will allow you to get away with this, some won't. But when you try things like this and things don't work properly you should focus on avoiding using undocumented settings.
I am afraid I can offer you no more help with this.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!