Re: Clarification on container security in OpenShift

2016-01-19 Thread Srinivas Naga Kotaru (skotaru)
; Cc: dev <dev@lists.openshift.redhat.com<mailto:dev@lists.openshift.redhat.com>> Subject: Re: Clarification on container security in OpenShift If you had specified uid 0 in your pod definition, you would receive an error (instead of being defaulted). We do this defaulting by default to protect from the

Re: Clarification on container security in OpenShift

2016-01-19 Thread Srinivas Naga Kotaru (skotaru)
e...@redhat.com>> Date: Tuesday, January 19, 2016 at 10:44 AM To: skotaru <skot...@cisco.com<mailto:skot...@cisco.com>> Cc: Paul Weil <pw...@redhat.com<mailto:pw...@redhat.com>>, dev <dev@lists.openshift.redhat.com<mailto:dev@lists.openshift.redhat.com>&g

Re: Clarification on container security in OpenShift

2016-01-19 Thread Clayton Coleman
uary 19, 2016 at 10:44 AM > To: skotaru <skot...@cisco.com> > Cc: Paul Weil <pw...@redhat.com>, dev <dev@lists.openshift.redhat.com> > > Subject: Re: Clarification on container security in OpenShift > > Not sure if this is exactly what you are asking, but Openshift al

Clarification on container security in OpenShift

2016-01-19 Thread Rishi Misra
Hello - as per: https://hub.docker.com/r/openshift/origin-custom-docker-builder/: "Containers run as a non-root unique user that is separate from other system users" In my experience I was able to run my Docker app image as a root user in OpenShift without modifying any security context. Perhaps