Closed C0rby closed 3 months ago
Starting oCIS via docker or systemd makes it a hard requirement to set either STORAGE_LDAP_CACERT
or STORAGE_LDAP_INSECURE
env variable for users without home directory. We should prioritize fixing this issue since it causes problems, e.g. in the web
CI and all the deployment examples
Usually services are run by a service user without a home directory. If that is the case then the default locations won't work and startup fails.
Steps to reproduce
Steps to reproduce the behavior:
- Create a system user
useradd -r ocis
- Run oCIS with that user
sudo -u ocis bin/ocis
- See that oCIS fails to start #
This is still an issue for our binary releases. Right now we document in the systemd documentation how to change the storage and configuration paths -> https://owncloud.dev/ocis/deployment/systemd/
Expected behavior
A sensible location should be used. Preferably all configuration files and resources should be stored in the same location.
This is the case now. Everything will be stored to the same directory.
Starting oCIS via docker or systemd makes it a hard requirement to set either
STORAGE_LDAP_CACERT
orSTORAGE_LDAP_INSECURE
env variable for users without home directory. We should prioritize fixing this issue since it causes problems, e.g. in theweb
CI and all the deployment examples
Is resolved
Supposedly fixed.
Describe the bug
The default location for
PROXY_TRANSPORT_TLS_CERT
,PROXY_TRANSPORT_TLS_KEY
,GLAUTH_LDAPS_CERT
andGLAUTH_LDAPS_KEY
is in the home directory of the user running ocis.Usually services are run by a service user without a home directory. If that is the case then the default locations won't work and startup fails.
Steps to reproduce
Steps to reproduce the behavior:
useradd -r ocis
sudo -u ocis bin/ocis
Expected behavior
A sensible location should be used. Preferably all configuration files and resources should be stored in the same location.