-
Notifications
You must be signed in to change notification settings - Fork 75
Open
Description
With the following securityContext set:
securityContext:
enabled: true
runAsUser: 1000
fsGroup: 2000
# Use this section to define additional pod security context values for primary Retool pods not provided by default.
# See this doc for options allowed here (ensure the Kubernetes version matches the version of the Kubernetes cluster you are deploying to): https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#podsecuritycontext-v1-core
extraSecurityContext:
runAsNonRoot: true
extraContainerSecurityContext:
allowPrivilegeEscalation: false
I get issues with retool starting up as it cannot make the required chmod changes on the startup scripts:
chmod: changing permissions of './docker_scripts': Operation not permitted
chmod: changing permissions of './docker_scripts/start_proxy.sh': Operation not permitted
chmod: changing permissions of './docker_scripts/stop_proxy.sh': Operation not permitted
chmod: changing permissions of './docker_scripts/start_dev_garden.sh': Operation not permitted
chmod: changing permissions of './docker_scripts/clash.yaml': Operation not permitted
chmod: changing permissions of './docker_scripts/start_api.sh': Operation not permitted
chmod: changing permissions of './docker_scripts/update_frontend.sh': Operation not permitted
chmod: changing permissions of './docker_scripts/wait-for-it.sh': Operation not permitted
chmod: changing permissions of './docker_scripts/odbc.ini': Operation not permitted
chmod: changing permissions of './docker_scripts/start_proxified.sh': Operation not permitted
chmod: changing permissions of './docker_scripts/odbcinst.ini': Operation not permitted
chmod: changing permissions of './docker_scripts/load_secrets_from_files.sh': Operation not permitted
Metadata
Metadata
Assignees
Labels
No labels