Message282503
| Author |
grahamd |
| Recipients |
Denis.Barmenkov, Jonathon Reinhart, Melissa Chang, aikinci, arekm, bbi5291, christian.heimes, eric.araujo, georg.brandl, grahamd, loewis, matrixise, nadeem.vawda, ned.deily, neologix, serhiy.storchaka, surajd, tarek, vstinner, xuanji, zaytsev |
| Date |
2016年12月06日.05:54:25 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1481003666.19.0.336185375873.issue10496@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
@surajd Why aren't you using the Python S2I builders for OpenShift?
When you run anything under OpenShift, it will assign your project a UID which any containers are forced to run under. The OpenShift containers include a mechanism using a package call nss_wrapper so that correct passwd entries are reported for the assigned UID. If your own image doesn't have a similar provision, and in general aren't designed to run as an arbitrary assigned UID, you will encounter various issues.
Read through the latter section of posts in:
* http://blog.dscpl.com.au/p/using-python-with-docker.html
for further details.
Anyway, this isn't the place to discuss OpenShift, use instead:
* https://groups.google.com/forum/#!forum/openshift
if you have questions about running Python under OpenShift. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年12月06日 05:54:26 | grahamd | set | recipients:
+ grahamd, loewis, georg.brandl, arekm, vstinner, christian.heimes, nadeem.vawda, tarek, ned.deily, eric.araujo, neologix, xuanji, bbi5291, Denis.Barmenkov, aikinci, serhiy.storchaka, matrixise, zaytsev, Jonathon Reinhart, Melissa Chang, surajd |
| 2016年12月06日 05:54:26 | grahamd | set | messageid: <1481003666.19.0.336185375873.issue10496@psf.upfronthosting.co.za> |
| 2016年12月06日 05:54:26 | grahamd | link | issue10496 messages |
| 2016年12月06日 05:54:25 | grahamd | create |
|