I would like to back up my nextcloud data using duplicati, but I absolutely can‘t figure out how to give Duplicati access to the Nextcloud volume. Both are running fine in separate Docker containers. I can’t figure out how to properly mount the volume, below is my current compose for duplicati. Do I need to mount the volume as source? Does it need to be declared or mapped separately?

---
version: "2.1"
services:
  duplicati:
    image: lscr.io/linuxserver/duplicati:latest
    container_name: duplicati
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=XXX
      - CLI_ARGS= #optional
    volumes:
      - /path/to/appdata/config:/config
      - /path/to/backups:/backups
      - /path/to/source:/var/lib/docker/volumes/073ac2751cd65ffd84750e578c38482905c3c7e4851a8cbb0bbbc5c33a285e84
    ports:
      - 8200:8200
    restart: unless-stopped
  • GlitzyArmrest@lemmy.worldEnglish
    5·
    1 year ago

    You might try adding :rw after each of your volume paths, like this:

    volumes:
      - /path/to/appdata/config:/config:rw

    My honest suggestion would be to ditch Duplicati for Duplicacy. Duplicacy is one time payment, but it’s much more polished than Duplicati. I actually had major issues with recovering files from Duplicati; sometimes it would work and sometimes it wouldn’t. Not ideal for something as critical as backup software.

    • skilltheamps@feddit.deEnglish
      2·
      1 year ago

      But it should not need write access to those files.

      I bet it is due to different UID. Nextcloud runs with the www-data user, and UID 1000 is likely whatever user OP set up on the host machine. Make Duplicati run with the same UID as nextcloud and it will have the permission to read the files.

        • __init__English
          1·
          1 year ago

          I just went through dockerizing my nextcloud installation. The www-data user on my host had uid 33, but the one inside the container uses uid 82, which had me scratching my head for a minute. You can confirm the actual uid by running id www-data inside the nextcloud container.

          • redcalcium@lemmy.instituteEnglish
            1·
            1 year ago

            I have two instances on two separate servers running and all of them use uid:gid 33:33 inside the container. I use the nextcloud:26-apache docker image.

            Edit: I think your container image is based on Alpine linux, which use uid 82 for its www-data user. Try switching to a debian-based image (e.g. the apache version) if you want it to match with your host system.

            • __init__English
              1·
              1 year ago

              Ah yep I bet that’s it, I’m using the alpine fpm image.

    • avnrt@lemmy.worldOPEnglish
      1·
      1 year ago

      Thanks! A drop down chevron has appeared next to the “Source Data” folder in duplicati, but it is still empty, showing neither the volume, nor its contents. Any idea what else I can try/modify?

      • MangoPenguin@lemmy.blahaj.zoneEnglish
        1·
        1 year ago

        Does it show the root / filesystem inside the container?

        You may need to update the folder permissions on the Nextcloud volume to allow all users to read data.

  • 7Sea_Sailor@lemmy.dbzer0.comEnglish
    1·
    1 year ago

    Why are you mounting the volume with the file system path, instead of the volume name? You should be able to mount the volume normally by specifying it in the volume section, i.e.

    services:
  duplicati:
    volumes:
      - nextcloud_data:ro

volumes:
  - nextcloud_data
    - external: true

    That should grant Duplicati read-only access to the entire volume without messing around with absolute file paths.

    • avnrt@lemmy.worldOPEnglish
      1·
      1 year ago

      Thanks, I didn’t fully understand the syntax before. I now see the volume in the duplicati GUI, but not its contents. When I just back up the entire volume, the backup size is basically zero (should be more like 800MB).