This is at least partly an SELinux issue. In docker-compose.yml under security_opt for both containers add “- label"disable” like:
security_opt:
- no-new-privileges:true
- label:disable
I’m still having an issue where the ownership isn’t getting set properly:
mattermost@0d4723e02e77:~$ ls -ln
total 640
-rw-r--r--. 1 2000 2000 2046 Jan 19 16:48 ENTERPRISE-EDITION-LICENSE.txt
-rw-r--r--. 1 2000 2000 598280 Jan 19 16:48 NOTICE.txt
-rw-r--r--. 1 2000 2000 7528 Jan 19 16:48 README.md
drwxr-xr-x. 2 2000 2000 37 Jan 19 16:49 bin
drwxr-xr-x. 2 65534 65534 6 Jan 25 15:58 bleve-indexes
drwxr-xr-x. 8 2000 2000 20480 Jan 19 16:48 client
drwxr-xr-x. 2 65534 65534 6 Jan 25 15:58 config
drwxr-xr-x. 2 65534 65534 6 Jan 25 15:58 data
drwxr-xr-x. 2 2000 2000 44 Jan 19 16:48 fonts
drwxr-xr-x. 2 2000 2000 4096 Jan 19 16:48 i18n
drwxr-xr-x. 2 65534 65534 6 Jan 25 15:58 logs
-rw-r--r--. 1 2000 2000 448 Jan 19 16:48 manifest.txt
drwxr-xr-x. 2 65534 65534 6 Jan 25 15:58 plugins
drwxr-xr-x. 2 2000 2000 4096 Jan 19 16:49 prepackaged_plugins
drwxr-xr-x. 2 2000 2000 4096 Jan 19 16:48 templates
But I will figure that out!