You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anything else we need to know:
The following error is seen in logs:
$ kubectl logs -n nextcloud nextcloud-dcc4678d9-gk9pd -fInitializing nextcloud 19.0.3.1 ...Initializing finishedNew nextcloud instanceInstalling with PostgreSQL databasestarting nextcloud installationCannot write into "config" directory!This can usually be fixed by giving the webserver write access to the config directoryOr, 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/19/go.php?to=admin-configsetting trusted domains…Cannot write into "config" directory!This can usually be fixed by giving the webserver write access to the config directoryOr, 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/19/go.php?to=admin-config
After applying the configuration the file/folder permissions looks like:
$ ls -la /ext/persistent/nextcloud/server/total 36drwxr-xr-x 9 1000 1000 4096 May 1 22:03 .drwxr-xr-x 5 1000 1000 4096 May 1 20:11 ..drwxr-xr-x 2 root root 4096 May 1 22:03 configdrwxr-xr-x 2 root root 4096 May 1 22:03 custom_appsdrwxr-xr-x 2 root root 4096 May 1 22:03 datadrwxr-xr-x 8 www-data root 4096 May 1 22:03 htmldrwxr-xr-x 4 root root 4096 May 1 22:03 rootdrwxr-xr-x 2 root root 4096 May 1 22:03 themesdrwxr-xr-x 2 root root 4096 May 1 22:03 tmp
$ ls -la /ext/persistent/nextcloud/server/config/total 8drwxr-xr-x 2 root root 4096 May 1 22:03 .drwxr-xr-x 9 1000 1000 4096 May 1 22:03 ..-rwx------ 1 root root 0 May 1 22:03 .htaccess-rwx------ 1 root root 0 May 1 22:03 apache-pretty-urls.config.php-rwx------ 1 root root 0 May 1 22:03 apcu.config.php-rwx------ 1 root root 0 May 1 22:03 apps.config.php-rwx------ 1 root root 0 May 1 22:03 autoconfig.php-rwx------ 1 root root 0 May 1 22:03 custom.config.php-rwx------ 1 root root 0 May 1 22:03 redis.config.php-rwx------ 1 root root 0 May 1 22:03 smtp.config.php
As a workaroung I can set the values via extraEnv:
AHA! I have been trying to figure this out for months, and this has to be the cause! I understand how frustrating this is, because it can also affect your backups. I don't have a fix, but maybe a workaround. 🤔
So, I don't know why it's created as root, but I do know that recently the community introduced a securityContext feature, that should let you force the container and/or pod to run as a different user, for instance 33 (this is the UID of the www-data user). You can check out the change in #269.
I currently have an issue open where I'm troubleshooting this in #335 if you have issues with it.
Describe the bug
When I configure
configs
for the first start in myvalues.yaml
file the permissions of theconfig
folder are set toroot:root
Version of Helm and Kubernetes:
Which chart:
nextcloud:2.6.1
What happened:
I wanted to set
overwritehost
andoverwriteprotocol
via an extra config file created in/var/www/html/config/
.What you expected to happen:
nextcloud starts with
config.php
andcustom.config.php
How to reproduce it (as minimally and precisely as possible):
Put the following lines of code into the
values.yaml
file:Anything else we need to know:
The following error is seen in logs:
After applying the configuration the file/folder permissions looks like:
As a workaroung I can set the values via
extraEnv
:But this is not how I expect that it should work like.
The text was updated successfully, but these errors were encountered: