Losing all Torrent-States when trying to update to a newer version

I am currently stuck at release 78da80ca-ls20. When updating the image to a newer version all torrents are gone, when I go back to 78da80ca-ls20 they re-appear. I tried going directly to latest and doing it step by step but it already broke at 5b398f77-ls22. The deluge config directory is bound to an internal HDD which is always present.

Expected Behavior

While updating the container the states of the torrents should be preserved.

Current Behavior

When updating to a newer version I lose all my torrent states.

Steps to Reproduce

Can provide a video if necessary.

Environment

OS: linux x86_64 Debian GNU/Linux 9 (stretch) Kernel: 4.9.0-12-amd64 CPU architecture: amd64
How docker service was installed: Package manager

Command used to create docker container (docker compose)

deluge:
    image: linuxserver/deluge:78da80ca-ls20
    container_name: deluge
    volumes:
      - /mnt/data/deluge/config:/config
      - /mnt:/downloads
    network_mode: "service:pia"
    restart: always
    depends_on:
      - pia
    environment:
      - PGID=0
      - PUID=0

Docker logs

Starting Version which has the states still available:

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-scripts: executing... 
[custom-init] no custom scripts found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[INFO    ] 13:17:34 configmanager:70 Setting config directory to: /config
[INFO    ] 13:17:34 ui:124 Deluge ui 1.3.15
[INFO    ] 13:17:34 ui:127 Starting web ui..
[INFO    ] 13:17:34 server:666 Starting server in PID 233.
[INFO    ] 13:17:34 server:679 Serving on 0.0.0.0:8112 view at http://0.0.0.0:8112
[INFO    ] 13:17:38 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:17:38 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:17:38 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:17:38 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:17:38 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[INFO    ] 13:17:38 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[INFO    ] 13:17:51 client:217 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 13:17:51 client:121 Connected to daemon at 127.0.0.1:58846..
[INFO    ] 13:17:51 pluginmanagerbase:158 Plugin Extractor enabled..
[INFO    ] 13:17:51 pluginmanagerbase:158 Plugin Scheduler enabled..

Starting version which has no states available (latest here):

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-scripts: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
13:20:00 [WARNING ][deluge.i18n.util           :83  ] IOError when loading translations: [Errno 2] No translation file found for domain: 'deluge'
13:20:00 [WARNING ][deluge.config              :475 ] Unable to open config file: /config/hostlist.conf because: [Errno 2] No such file or directory: '/config/hostlist.conf'
13:20:00 [WARNING ][deluge.config              :500 ] Unable to backup old config: [Errno 2] No such file or directory: '/config/hostlist.conf'
Unhandled error in Deferred:

After restarting the container again with latest, the errors regarding hostlist.conf disappear, as the file was created by deluge on the first start.

linuxserver / docker-deluge