[BUG] Impossible do the backups with latest version (v2.1.0.2_beta_2024-11-29-ls225)

PacmanForever commented 9 hours ago

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Execute any backup and always appears the same error from the last update.

Expected Behavior

No errors.

Steps To Reproduce

Execute backup
Wait some minuts
Appears the error

Environment

Docker in Linux Ubuntu 24.04

CPU architecture

x86-64

Docker creation

duplicati:
        restart: unless-stopped
        container_name: duplicati
        ports:
            - '8200:8200'
        environment:
            - PUID=0
            - PGID=0
        volumes:
            - '/dockerData/Duplicati/config:/config'
            - '/dockerData/Duplicati/backups:/backups'
            - '/dockerData:/source'
        networks:
          custom_network:
            ipv4_address: 172.19.0.3
        image: lscr.io/linuxserver/duplicati:latest

Container logs

One or more errors occurred. (The file duplicati-ieb1bc528c7b4404592c80d5ce3cae324.dindex.zip.aes was uploaded but the returned size was -1 and it was expected to be 7949 (The file duplicati-ieb1bc528c7b4404592c80d5ce3cae324.dindex.zip.aes was uploaded but the returned size was -1 and it was expected to be 7949) (One or more errors occurred. (The file duplicati-ieb1bc528c7b4404592c80d5ce3cae324.dindex.zip.aes was uploaded but the returned size was -1 and it was expected to be 7949)))

github-actions[bot] commented 9 hours ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

j0nnymoe commented 9 hours ago

You need to check duplicati's documentation on how to deal with those errors.

PacmanForever commented 9 hours ago

Until last weekend everything was fine, the only change was the update to the latest version. To make matters worse, the latest version changed the version of the duplicati database and I can't roll back to the penultimate version. For me this is an issue.

j0nnymoe commented 9 hours ago

Yes I get this is an issue. We package what duplicati release, this does not look like a container issue to me but an application issue. You need to see if this bug has been reported to duplicati but from my quick googling, it seems a common problem going back years.

PacmanForever commented 9 hours ago

Okay, I understand that we only need to put container errors here.

PacmanForever commented 8 hours ago

Just to mention that I put the original image (duplicati/duplicati:latest) and everything works perfectly. Are you sure it's not an error with this image?

thespad commented 7 hours ago

That image is over 6 months old as they stopped pushing the latest tag back in May.

See https://hub.docker.com/r/duplicati/duplicati/tags

linuxserver / docker-duplicati