Open jennec opened 8 months ago
Two possible issues here, either the fast permissions check is finding a permission issue so it's try to run the full check to rectify (are you using network storage but any chance) or you've not recreated the docker containers after changing the value in the env file. Did you run docker compose up -d
?
I have a SMB share mounted to a local folder for the cache location.
I’ve destroyed and recreated the containers each time I made a change to the ENV file or to the docker-compose file.
I only enabled this setting because I initially had permissions problems with the mount. Prior to that it was not doing a full permissions check. Once I sorted the permissions issue it this problem started.
Does monolith log why it decided to do the full perm check anywhere when it starts up?
Describe the issue you are having
FORCE_PERMS_CHECK = false does not stop Full Permissions Check at start up after initially enabling it.
Removing the variable from the ENV file or directly from the container does not stop the check from happening.
How are you running the container(s)
ENV File
DNS Configuration
Output of container(s)