Andrew O.

Actually. the UBI9 python image in question [sets](https://catalog.redhat.com/software/containers/ubi9/python-39/61a61032bfd4a5234d59629e?image=66995897977b6ac3132be0f7&container-tabs=dockerfile) USER to 1001, so I'm not sure where the UID 1234 is coming from yet.

Some new findings & a temporary workaround (for this specific devfile) below. The UID 1234 was coming from the [default](https://github.com/devfile/devworkspace-operator/blob/533d1f0510b4dcfaee8682e5e0b8103812f79cfe/pkg/config/defaults.go#L82C1-L89C71) pod security context used by DevWorkspace Operator on Kubernetes: ```go...

@tolusha See my above [comment](https://github.com/eclipse-che/che/issues/23179#issuecomment-2397434938). It's not clear yet if this is a DWO bug or a chectl (default che cluster cr on minikube/kubernetes) bug. Further investigation and discussion still...

> I tend to think it rather DWO bug then a chectl. > I believe we have to document the requirements related to UID. @tolusha I agree, I think the...

@ronaldor1968 as a workaround, I suggest either using the quay.io/devfile/universal-developer-image:ubi8-latest (you can specify a custom image in the Dashboard's UI when creating a workspace) or configuring the Che Cluster CR...