ehough / docker-duplicacy Goto Github PK

Perhaps not related to this project at all, more like a docker/linux issue in general, but I'm unable to create any files when using the cap_drop: ALL feature.

Is the the intent that all config files should be already created before adding the cap_drop switch?

  duplicacy:
    image: "erichough/duplicacy:1.1.0"
    container_name: duplicacy
    env_file:
      - secrets/file-permissions.env # PGID = 1000; PUID = 1000
    cap_drop:
      - ALL
    ports:
      - 3875:3875
    restart: always
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "/etc/timezone:/etc/timezone:ro"
      - "/mnt/Software/Linux/duplicacy/duplicacy-config:/etc/duplicacy"
    command: "touch /etc/duplicacy/123"

lilja@devnode:~/homelab$ docker-compose up duplicacy
Recreating duplicacy ...
Recreating duplicacy ... done
Attaching to duplicacy
duplicacy               | touch: /etc/duplicacy/123: Permission denied

And removing the cap_drop with the touch, it works:

lilja@devnode:~/homelab$ docker-compose up duplicacy
Recreating duplicacy ...
Recreating duplicacy ... done
Attaching to duplicacy
duplicacy exited with code 0

Running ls -l /etc/duplicacy with cap_drop.

lilja@devnode:~/homelab$ docker-compose up duplicacy
Removing duplicacy
Recreating f5bea9e64d8e_duplicacy ...
Recreating f5bea9e64d8e_duplicacy ... done
Attaching to duplicacy
duplicacy               | total 4
duplicacy               | drwxr-xr-x    2 1000     1000             0 Jan 19 16:13 .
duplicacy               | drwxr-xr-x    1 root     root          4096 Jan 22 20:03 ..
duplicacy exited with code 0

I created a Duplicacy container, changed some settings, then inspected my duplicacy.json file in /etc/duplicacy and it is still blank. Restarted the container multiple times, and while my config is retained on the web UI it is not reflected in /etc/duplicacy.

I opened a terminal into the container and I am seeing the correct settings stored in ~/.duplicacy-web/duplicacy.json.

Hi Eric

Thanks for the docker container and for keeping it updated. Appreciated. Is there a way I can access the container command line (for other containers I would use the exec it command with /bin/bash and can access the command line of the container). Thanks again.

Hi, I am currently using "saspus/duplicacy-web", and the container is using UTC instead of my local timezone.
I picked between "erichough/duplicacy" and "saspus/duplicacy-web" purely by usage count.

Looking at the config, I suspect I will have the same issue with your container.

Can you please honor the TZ environment variable, and set it in the container, such that the web UI and scheduling uses my local timezone, not UTC?

E.g. log from Unraid creating the container:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='duplicacy-web' --net='host' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'USR_ID'='99' -e 'GRP_ID'='100' -v '/mnt/user/appdata/duplicacy-web/config/':'/config':'rw' -v '/mnt/user/appdata/duplicacy-web/logs/':'/logs':'rw' -v '/mnt/user/appdata/duplicacy-web/cache/':'/cache':'rw' -v '/mnt/user/':'/backuproot':'ro' 'saspus/duplicacy-web' 

2f0a27f1b00e89b77f9b1927d8904c43df4e3d0a4d9a025deac3c0d945d6a6c6

Note the TZ variable that is automatically added by Unraid.

It also looks like the logs are not externalized in your container, maybe consider doing that so that historic data is preserved between container updates, or did I miss it in config?

It looks like what's happening is that the web ui deletes and re-creates the duplicacy.json file whenever you change a schedule (and probably other settings).

This means that the ln -s links you create in the Dockerfile ENTRYPOINT will correctly load the settings when the container is first run, but any changes in the web ui cause the link to be deleted and a new unlinked file to be created in ~/.duplicacy-web/duplicacy.json.

This essentially prevents one from making changes in the web-ui and having them persist across container reboots.

Not totally sure how to solve this.

Hey,

Love this docker image for my x86-64 machines, but would love to use it on my Pi rather than having to run the package natively.

Any chance of a separate build for pis?

Thanks,
Brett

Any chance of having Duplicacy auto-update on boot with this container?