Username resolution failing

Hi. Regarding openshift policy for safely running images, it's recommended to disable scc for unprivileged user. This may causes some issues while reading from password database since EUID of the running user is generated by openshift and can't be found inside the container: bash-4.2$ pip

Re: Username resolution failing

Yes there is a trick, documented here: https://docs.openshift.org/latest/creating_images/guidelines.html#openshift-specific-guidelines see the section on "*Support Arbitrary User IDs" *which describes how to use nss wrapper to work around this. That said, the openshift python image already does

Re: Username resolution failing

Yes, we are using rhel images. Thanks! *Mateus Caruccio* Master of Puppets +55 (51) 8298.0026 gtalk: *mateus.caruc...@getupcloud.com twitter: @MateusCaruccio * This message and any attachment are solely for the intended recipient

Re: Username resolution failing

That's a good point. We do have the mechanism in place to do that. Michal, any objection to adding the NSS env definitions to our scl_enable script? On Tue, Jan 19, 2016 at 11:02 AM, Mateus Caruccio < mateus.caruc...@getupcloud.com> wrote: > Yep, just tried centos images and it is working

Re: Username resolution failing

Yep, just tried centos images and it is working fine. It took me a while to understand the whole thing. I was simply "oc exec-ing" into the pod, but those NSS vars are create by sti/run. It may be good if those vars would be available from any shell. Thanks. *Mateus Caruccio* Master of Puppets