Cannot Write Into "config" directory

[jwall87]

Hello,

I'm using Unraid and grabbed your Docker from the Community App Store.

When running, I see the following in my logs:

 Executing Cron Tasks: Fri Mar  8 21:15:00 UTC 2024
-------------------------------------------------------------
> Nextcloud Container ID: 1259567c48db
> Running Script: ./run-cron-php.sh
Cannot write into "config" directory!
This can usually be fixed by giving the web server write access to the config directory.

But, if you prefer to keep config.php file read only, set the option "config_is_read_only" to true in it.
See https://docs.nextcloud.com/server/28/go.php?to=admin-config
> Done

Any advice? I've tried to add the cron docker to the Nextcloud PHP config as follows:

  'trusted_proxies' => 
  array (
    0 => 'NginxProxyManagerOfficial',
    1 => 'Nextcloud-cronjob',
  ),

This is the error log directly from nextcloud:

I just cant seem to figure it out. Thank you!!

[nixmomo]

did you resolved this? I have the same issue

[haxxorboi]

Ran into the same issue as well. I think I tracked it down to the mismatch between unraid's default user 99:100 (nobody) (and specified in the nextcloud container user parameters) and the one being using by nextcloud normally and included in the community template (www-data).

I changed the env NEXTCLOUD_EXEC_USER to be 99, set interval to 1, and now it seems to be running properly per the log (or at least no longer throwing those errors. ("nobody" might also work but I just went with 99, as when I tried to match user 99 inside the nextcloud container console I got no matching user name.)

Nextcloud's cronpage also is no longer reporting that cron hasn't run for 3 days now, but I don't know for sure if this is just a fluke or a long term fix.

Note: I don't suggest leaving at 1 min interval, but it allows monitoring the log entries to see if the error stops being thrown quickly.

Env variables used:
-e 'NEXTCLOUD_CONTAINER_NAME'='nextcloud'
-e 'NEXTCLOUD_CRON_MINUTE_INTERVAL'='1'
-e 'NEXTCLOUD_EXEC_USER'='99'
-e 'NEXTCLOUD_EXEC_SHELL'='bash'

[Bluefish67]

This also helped me to eliminate the error with “env NEXTCLOUD_EXEC_USER to 99”.

Should be included in the documentation.

Thanks @haxxorboi