In CodeScene version 6.5.6, the codescene user/group UID/GID was changed to 10999 (previously 999).
Usually, UIDs below 1000 should be reserved for the system and not used by normal applications, thus following Docker's best practices, we decided to make this change.
Normally, this change would go unnoticed, and customers won't have issues, because our startup script should take care of the permission fixes and changing the owner of the files/folders to 10999.
However, due to different setups, the customers may experience issues such as running the analysis for the existing projects, getting an error that a folder is not writeable anymore, a failure when starting CodeScene after the upgrade, and similar. The root cause lies in the permissions, and in this case, checking the file system permissions is needed.
The ownership of the files and directories where CodeScene data is stored must be updated to match the new UID (10999) and GID (10999) used in the updated Docker image.
When checking the file system permissions, it's good to start with /codescene all the way down to all the important folders such as:
/codescene/analysis/codescene/repos/codescene/diagnostics...
All of that is inside the docker volume.
Ensuring that the CodeScene process inside the Docker container has the correct access permissions should resolve the issue.