Closed djayor closed 7 months ago
It looks like something is outdated on your end for the ARM64 machine.
Removing core plugin erasedata...
This was deprecated when the erasedata
plugin on ruTorrent was improved.
This line here is where your tripping at for the .rtorrent.rc
file being reset.
https://github.com/crazy-max/docker-rtorrent-rutorrent/blob/1efb9e087f90f68ed132b3ffd419b29145a1838e/rootfs/etc/cont-init.d/03-config.sh#L196
I removed the container, and the image and did a clean install. Tonight the same happened, the container was updated and the torrent list was cleaned again.
Should I comment the line 196 to 199 ?
I'm not able to repro after bump to latest. Closing this one in the meantime but feel free to continue the discussion if it still occurs on your side.
Support guidelines
I've found a bug and checked that ...
Description
My containers are updated whenever a new version is released via Watchtower. I currently have 3 machines, 2 with ARM64 and another with AMD64. Whenever the container is updated on ARM64 machines, the torrent list is removed and the /data/rtorrent/.rtorrent.rc file is reset to default.
Expected behaviour
It is expected that after the update the torrent list and the .rtorrent.rc file will remain intact. On AMD64 machines the list remains and the file are intact after the update.
Actual behaviour
But on machines with the ARM64 tag, the torrent list is removed, and .rtorrent.rc is reset to default.
Steps to reproduce
This happens without my intervention only after updating. Even if you don't use the watchtower to perform the automatic update and manually edit the image of crazymax/rtorrent-rutorrent:current to crazymax/rtorrent-rutorrent:latest on the portainer.
Docker info
Docker Compose config
No response
Logs
Additional info
If the information is incomplete, I can provide more data. Thanks