Watchlistarr disregarding config.yaml

[adamblaine]

My config.yaml is set up correctly and I've uncommented everything I wanted to edit, including the section headers. But when I restart docker, it only takes into account what I've changed in the docker compose file. Nothing I've included in the config file is taken into account.

If I look at the files inside the docker container, under /app/config/config.yaml I can see the config.yaml with the edits I made to it. It just disregards it and uses docker variables + default settings when run.

I had to add variables like "SONARR_ROOT_FOLDER" to my docker compose in order to change that from the default setting.

Is there a fix to get the config file to take priority? Or is there a full list of available variables I can just add in to the docker compose file? I'm specifically wanting to modify the deleteFiles, radarrTagIDs, etc.

[fyve5]

I had a similar issue. I missed uncommenting a section heading. Use https://www.yamllint.com/ to validate your config.yaml. interval: sonarr: radarr: tags: plex: all had to be uncommitted for the file to be parsed.

[petercockroach]

I spent way too much time trying to figure this one out. I created a PR to uncomment the services in the template.

[andreypopov]

I have similar issue, I set volume mount but in /app/config/config.yaml I don't see my edited file. There is default one with all commented strings.

I have very simple yaml, it is correct, in debug logs:
23:36:35.588 [main] DEBUG c.FileAndSystemPropertyReader$ - Failed to read from config.yaml: null

[andreypopov]

The reason was, that I started docker compose as root, watchlistarr folder had root:root permissions, because of it it was not possible to read the config.

Solution was:
sudo -R chown server:server watchlistarr_config_folder