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
Hi 👋 I'm trying to run Seafile Pro on Kubernetes by installing it via a handcrafted Helm chart.
The issue I am encountering is that Seafile attempts to generate configuration files on startup. The environment variables that can be used to influence that config-generation step are not sufficient (such as S3 configuration), so I would like to generate the configuration files via Helm and put them into the appropriate place.
However, I can't get Seafile to not try and generate these files, and it always fails with en error like this:
Traceback (most recent call last): File "setup-seafile-mysql.py", line 1598, in <module> main() File "setup-seafile-mysql.py", line 1547, in main seafile_config.generate() File "setup-seafile-mysql.py", line 933, in generate with open(self.seafile_conf, 'w') as fp: OSError: [Errno 30] Read-only file system: '/opt/seafile/conf/seafile.conf'
That's because the configuration files are mounted into the container by Kubernetes.
Setting them to readOnly: false doesn't help. When the container restarts, those changes would be lost but Seafile is not going to configure itself another time. Also it would require that the container "merges" with the existing configuration and prefers it.
Ideally there would be an option for the container to entirely skip config generation, yet Database initialization should still happen.
It would also need to skip any Mysql "root" checks, as I wouldn't be giving it any root credentials. I can make sure the seafile user exists when Seafile starts up.
The text was updated successfully, but these errors were encountered:
Hi 👋 I'm trying to run Seafile Pro on Kubernetes by installing it via a handcrafted Helm chart.
The issue I am encountering is that Seafile attempts to generate configuration files on startup. The environment variables that can be used to influence that config-generation step are not sufficient (such as S3 configuration), so I would like to generate the configuration files via Helm and put them into the appropriate place.
However, I can't get Seafile to not try and generate these files, and it always fails with en error like this:
That's because the configuration files are mounted into the container by Kubernetes.
Setting them to
readOnly: false
doesn't help. When the container restarts, those changes would be lost but Seafile is not going to configure itself another time. Also it would require that the container "merges" with the existing configuration and prefers it.Ideally there would be an option for the container to entirely skip config generation, yet Database initialization should still happen.
It would also need to skip any Mysql "root" checks, as I wouldn't be giving it any root credentials. I can make sure the
seafile
user exists when Seafile starts up.The text was updated successfully, but these errors were encountered: