Restricted now drops the SETGID capability. The "anyuid" SCC does not. You can edit restricted to give that or grant the user anyuid (which is more correct).
On Mar 4, 2016, at 12:31 AM, Dean Peterson <[email protected]> wrote: In previous versions of openshift origin I was able to run an nginx server with some static content inside a container. Now I install with the ansible installer and I get the following error in the nginx errors.log inside the running container. 2016/03/03 23:51:22 [emerg] 6#0: setgid(996) failed (1: Operation not permitted) 2016/03/03 23:51:22 [alert] 5#0: worker process 6 exited with fatal code 2 and c annot be respawned fsfsfadf My nginx.conf file is: user nginx; worker_processes 1; error_log /var/log/nginx/error.log warn; pid /var/run/nginx.pid; events { worker_connections 1024; } http { include /etc/nginx/mime.types; default_type application/octet-stream; log_format main '$remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for"'; access_log /var/log/nginx/access.log main; sendfile on; #tcp_nopush on; keepalive_timeout 65; #gzip on; } daemon off; I have set my scc restricted runAsUser.type to RunAsAny. Is there something else I need to do to allow setgid(996) for nginx in origin? I have _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
