Document how to configure devfile to get terminals in any images on OCP 4.x

[slemeur]

Is your task related to a problem? Please describe.

We have been having issues with the images on OCP 4: #13977

We need to provide guidance to the community on how to configure the images and how is this possible directly from the devfile.

[tsmaeder]

If we fix our images for 7.0, we need to tell the community how to do it.

[amisevsk]

The only thing necessary is what's documented for OpenShift 3.11 "Support Arbitrary User IDs" but I agree that this should be present in Che docs.

AFAIK it's not possible to configure this from the devfile, the issue is CRI-O on OCP 4.1 writing an entry in /etc/passwd that uses /sbin/nologin as a login shell. More investigation is necessary for an actual solution there.

To be clear, our images (in the devfile registry) are fixed and working on 4.1.

[slemeur]

Right, but the issue is that if someone is using Che on OpenShift, he can't use the images he wants, he has to modify them in order to handle those specifics. So even if our default devfile are working, anybody trying to create its own devfile and not rely on the default che images will have to troubleshoot this. That's why the doc is very important until we have a better solution in place.

…

On Thu, Jul 25, 2019 at 8:43 PM Angel Misevski ***@***.***> wrote: The only thing necessary is what's documented for OpenShift 3.11 "Support Arbitrary User IDs" <https://docs.openshift.com/container-platform/3.11/creating_images/guidelines.html#openshift-specific-guidelines> but I agree that this should be present in Che docs. AFAIK it's not possible to configure this from the devfile, the issue is CRI-O on OCP 4.1 writing an entry in /etc/passwd that uses /sbin/nologin as a login shell. More investigation is necessary for an actual solution there. To be clear, our images (in the devfile registry) are fixed and working on 4.1. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#14020>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMPTILHIUQB7A26WB5HNE3QBHX4BANCNFSM4IGYZT7Q> .

-- Stévan LeMeur // Product Manager // Developer Tools // +336-87-11-27-55

[slemeur]

@rkratky : Is that something your team would be able to pick up?

[l0rd]

Changed milestone to 7.1.0

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.