Podman login into internal OpenShift registry doesn't work if `PersistUserHome ` is enabled

[tolusha]

Describe the bug

Podman login into internal OpenShift registry doesn't work if PersistUserHome is enabled

Che version

7.92@latest

Steps to reproduce

1. Start an empty workspace on DogFooding Cluster
2. Run in the terminal podman login image-registry.openshift-image-registry.svc:5000
3. Obtain expected result

Authenticating with existing credentials for image-registry.openshift-image-registry.svc:5000
Existing credentials are valid. Already logged in to image-registry.openshift-image-registry.svc:5000

4. Stop the workspace
5. Start the workspace again
6. Run in the terminal podman login image-registry.openshift-image-registry.svc:5000
7. Obtain unexpected result, which mean that automatic podman login into internal registry failed:

Username: 

Expected behavior

User successfully logged into internal OpenShift registry

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Linux

Eclipse Che Logs

No response

Additional context

Solution: Replace https://github.com/eclipse-che/che-dashboard/blob/main/packages/dashboard-backend/src/devworkspaceClient/services/podmanApi.ts#L92-L93 with export SSL_CERT_DIR=/var/run/secrets/kubernetes.io/serviceaccount

[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.