??{{rw-rw-rw- 1 root mysql 10765 Mar 23 14:01 writeengineserver.log
rw-rr- 1 root mysql 471972 Mar 23 14:01 info.log
rw-rr- 1 root mysql 3780129 Mar 23 14:02 warning.log
rw-rw-rw 1 root mysql 1836792 Mar 23 14:02 exemgr.log
rw-rw--- 1 root mysql 1264906 Mar 23 15:01 mariadb-error.log
rw-rr- 1 root mysql 1048483 Mar 23 15:35 cmapi_server.log.1
rw-rw-rw 1 root mysql 2200059 Mar 23 15:41 cmapi_server.log.2
rw-rr- 1 root mysql 158884 Mar 23 15:41 cmapi_server.log}}??
toddstoffel petko.vasilev
above is what I see on the cluster that i created with the latest sky version. Note that not only CS but ES logs are the same root owner.
I presume that owner(=root) and group owner(=mysql) are derived from account that starts the top process in the process tree.
Is that determined at docker build time ? via
USER root
WORKDIR /opt
Is that affected somehow by k8s ?
Priority of this is already minor , but I am going to ask pramod.mahto@mariadb.com what practical problems does this present
alexey.vorovich In general DBA want to cycled and archive these log files on regular interval of time, doing that using non-root user not possible. They need to involve sysadmin team , generally they don't want to do that.
pramod.mahto@mariadb.com Yes, I absolutely understand the need to access files 
. I am just trying to understand various types of access control. I login via VSCODE terminal option (I believe it is the same as kubectl) and i am root .
[root@cs-node-0 /]# id
uid=0(root) gid=0(root) groups=0(root)
[root@cs-node-0 /]#
Your example is also in Sky , correct ?
Fixed in version 23.02