docker-transmission-openvpn icon indicating copy to clipboard operation
docker-transmission-openvpn copied to clipboard

Rename doesn't persist after updating image

Open jhskim78 opened this issue 3 years ago • 0 comments

Is there a pinned issue for this?

  • [X] I have read the pinned issues and could not find my issue

Is there an existing or similar issue/discussion for this?

  • [X] I have searched the existing issues
  • [X] I have searched the existing discussions

Is there any comment in the documentation for this?

  • [X] I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to a provider?

  • [X] I have checked the provider repo for issues
  • [X] My issue is NOT related to a provider

Are you using the latest release?

  • [X] I am using the latest release

Have you tried using the dev branch latest?

  • [ ] I have tried using dev branch

Docker run config used

docker run --cap-add=NET_ADMIN -d -v :/data -e OPENVPN_PROVIDER={provider} -e OPENVPN_CONFIG={config file} -e OPENVPN_USERNAME={username} -e OPENVPN_PASSWORD={password} -e LOCAL_NETWORK=192.168.0.0/16 -e PUID=1005 -e PGID=1001 -e TZ=Australia/Melbourne --log-driver json-file --log-opt max-size=10m -p 9091:9091 --restart always --name transmission haugene/transmission-openvpn

Current Behavior

In transmission, there is the "Rename" and "Set Location" options to rename a file or folder to something different to the torrent name, and seed from a location other than /data/completed/.

After an image upgrade, all renamed and relocated files cannot be found, and Transmission expects them in /data/completed/

The issue can be reproduced using the following steps:

  1. in transmission, rename and/or relocate a torrent
  2. docker stop transmission // when using --name transmission as per the docker config above
  3. docker rm transmission
  4. docker pull haugene/transmission-openvpn
  5. docker run ... // as per docker run command above

Expected Behavior

After an image upgrade, the renamed/relocated files can be found by transmission.

How have you tried to solve the problem?

I've no idea how to solve this problem. I assume the files that transmission use to track the location/rename do not live in the /data folder in the container.

Log output

N/A

HW/SW Environment

- OS: Debian 10 (buster) 4.19.249-2
- Docker: Docker Engine - Community 20.10.17

Anything else?

No response

jhskim78 avatar Aug 11 '22 19:08 jhskim78