Crio runs with umask 0000 causing the files inside Pod has wrong permission
Issue
- Crio runs with umask 0000 causing the files inside Pod has wrong permission
- The issue happens to particular node, which means all the Pods running on particular node are affected
- To figure out which processes are running with umask 0000:
$ sudo ps lp $(grep -l "Umask:[[:space:]]0000" /proc/[0-9]*/status | cut -f3 -d/) | grep -v "]$"
- The /etc/resolv.conf inside the Pod has 666 permission
Environment
- Red Hat OpenShift Container Platform 4.10 and above
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.