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
Jeedom runs on NGINX, so with the www-data user. To allow to execute all administration tasks from the browser, all Jeedom files must be owned by the www-data user (it's totally unsecure, but it's builds like that).
With these Docker images ( jeedom-data and jeedom-all-in-one ), after the installation and/or updates when the container starts, all Jeedom file permissions are messed up. The owner of Jeedom files is/becomes root instead of www-data. So Jeedom is not able to run properly.
Fix the file ownership manually is not a durable solution because, later on startup during the next update, the files ownership will be messed up again.
To fix it, in the /docker-entrypoint.sh script (or in /entrypoint.sh on an existing container), replace:
Jeedom runs on NGINX, so with the
www-data
user. To allow to execute all administration tasks from the browser, all Jeedom files must be owned by thewww-data
user (it's totally unsecure, but it's builds like that).With these Docker images (
jeedom-data
andjeedom-all-in-one
), after the installation and/or updates when the container starts, all Jeedom file permissions are messed up. The owner of Jeedom files is/becomesroot
instead ofwww-data
. So Jeedom is not able to run properly.Fix the file ownership manually is not a durable solution because, later on startup during the next update, the files ownership will be messed up again.
To fix it, in the
/docker-entrypoint.sh
script (or in/entrypoint.sh
on an existing container), replace:by:
All files ownership problems will be fixed durably without altering Jeedom's installation/update scripts.
The text was updated successfully, but these errors were encountered: