permission denied to /updater/data/updates.json

[Taseen18]

I get this error message in the logs when I attempt to startup. I have posted an issue on the issues tab. Anyone else experienced this?

2023-01-09T17:02:31Z ERROR open /updater/data/updates.json: permission denied
2023-01-09T17:02:31Z INFO Shutdown successful

[tgaertner]

Had the same error.

Go to your docker settings and change

Config: from "/mnt/user/appdata/ddns-updater" to "/mnt/user/appdata/ddns-updater/data"

At least it solved it for me.

[haferm]

had the same, follow the exact setup procedure.. https://github.com/qdm12/ddns-updater#setup

[daendaen]

I would like to use the ddns updater under unraid

I created the config.json file. but still get the error message

[tgaertner]

What is the value for your "Config" setting like? (I didn't touched the advanced settings)

[daendaen]

the problem was because of the authorization of the folder. it was set to nobody 99. this seems to be the default for unraid. I then changed s to 1000, now everything works

[andymaycoates]

I had a similar issue on my Synology NAS where the container log informed me that updates.json could not be created due to a permissions issue. I found that the container was trying to write the updates.json file with the UID:GID of 1000:1000, which did not exist on my NAS. You can see these args in the Dockerfile, and they cannot be replaced by ENV variables.

To fix this issue, I noted the UID:GID of another suitable NAS user (ensuring that said user had write permissions on the share mapped to /updater/data in the container) and then instructed my docker-compose file to build the container instead of pulling an image. This allowed me to supply args to change the UID and GID. Here is an example of my docker-compose file:

version: "3.7"
services:
  ddns-updater:
    build:
      context: https://github.com/qdm12/ddns-updater.git
      args:
        UID: 1026 # Substitute for a user on your NAS
        GID: 100 # Substitute for the user's group on your NAS
    #image: qmcgaw/ddns-updater
    container_name: ddns-updater
    network_mode: "bridge"
    ports:
      - 9988:9988/tcp
    volumes:
      - /volume1/docker/ddns-updater/data:/updater/data
    environment:
      - CONFIG=
      - PERIOD=5m
      - UPDATE_COOLDOWN_PERIOD=5m
      - PUBLICIP_FETCHERS=all
      - PUBLICIP_HTTP_PROVIDERS=all
      - PUBLICIPV4_HTTP_PROVIDERS=all
      - PUBLICIPV6_HTTP_PROVIDERS=all
      - PUBLICIP_DNS_PROVIDERS=all
      - PUBLICIP_DNS_TIMEOUT=3s
      - HTTP_TIMEOUT=10s      
           # Web UI
      - LISTENING_PORT=9988
      - ROOT_URL=/
      - HEALTH_SERVER_ADDRESS=127.0.0.1:9995
      # Backup
      - BACKUP_PERIOD=0 # 0 to disable
      - BACKUP_DIRECTORY=/updater/data
      # Other
      - LOG_LEVEL=info
      - LOG_CALLER=hidden
      - SHOUTRRR_ADDRESSES=
    restart: always

You'll need to make sure you have Git installed before doing the above. I just installed Git Server using the Synology Package Center; no other config required.

[qdm12]

Documenting the answer for any future user encountering this issue. Usually you did not read properly essentially step 1 of the Setup section in the readme. All the following is said there, but it's detailed more below:

• You don't need a user with uid 1000 and gid 1000 to run these commands normally. I don't, and I still make the data directory owned by user id 1000, and it works. But some systems such as Unraid might require this, especially outside the terminal and through graphical user interfaces.
• PUID, PGID, UID or GID do NOT exist in this Docker image, and they don't do anything. The image is without a base system and is pre-built to run as user 1000 (and it's not root downgrading to non-root, for security purposes).
• If you want to pick something else than uid 1000, you have to build the Docker image yourself, you can use for example docker builld -t qmcgaw/ddns-updater --build-arg UID=765 https://github.com/qdm12/ddns-updater.git#v2.5.0 to build the image for tag v2.5.0 and for UID set to 765.
• If you don't really care about the container running without root for security purposes, you can run it as root user --user=0 or --user=root (or user: 0 in docker-compose.yml) and that will work too, and you won't have to build a custom image.