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
One requirement of the “Restricted” policy is setting allowPrivilegeEscalation to false. However, our MSSQL container image fails to run under this configuration and raises the following error:
SQL Server 2022 will run as non-root by default.
This container is running as user 1003350000.
Your master database file is owned by 1003350000.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
/opt/mssql/bin/permissions_check.sh: line 60: /opt/mssql/bin/sqlservr: Operation not permitted
/opt/mssql/bin/permissions_check.sh: line 60: /opt/mssql/bin/sqlservr: Success
Below is the relevant patch we applied to our StatefulSet:
We also assigned the microsoft-sql-server SCC to the mssql-ref service account, but this did not resolve the issue. According to Microsoft’s documentation (bdc-scc.yaml example) MSSQL requires allowPrivilegeEscalation to be set to true, and overriding these settings would break core functionality.
Is there any way to enforce the “Restricted” PSS policy?
The text was updated successfully, but these errors were encountered:
Our penetration test team has requested that we enforce the “Restricted” PSS policy by adding the following labels to the namespace:
One requirement of the “Restricted” policy is setting allowPrivilegeEscalation to false. However, our MSSQL container image fails to run under this configuration and raises the following error:
Below is the relevant patch we applied to our StatefulSet:
We also assigned the microsoft-sql-server SCC to the mssql-ref service account, but this did not resolve the issue. According to Microsoft’s documentation (bdc-scc.yaml example) MSSQL requires allowPrivilegeEscalation to be set to true, and overriding these settings would break core functionality.
Is there any way to enforce the “Restricted” PSS policy?
The text was updated successfully, but these errors were encountered: