Andrew O.

@ibuziuk: @deerskindoll is correct, this has not been resolved. Though it's still debatable whether this is worth documenting: > We may not want to document this attribute, as it is...

It seems like `/home/user/.config/containers/storage.conf` is missing, but `/home/tooling/.config/containers/storage.conf` is present. For some reason, it seems like the [stow command](https://github.com/devfile/developer-images/blob/b6ef89548129f8981f9a15334b4ff73ccc767491/universal/ubi8/Dockerfile#L458-L459) ~~in the Dockerfile itself is not creating a symbolic link for...

What's weird is that the git blame regarding the `storage.conf` files in the Dockerfile show they haven't been touched in months (for some lines, in years)...

Thank you for the valuable info @dkwon17 :pray: David and I made some more findings regarding this bug: As mentioned, `persistUserHome` needs to be enabled in the Che Cluster CR....

This issue should be resolved now that https://github.com/devfile/devworkspace-operator/pull/1251 is merged. Once the nightly build of DevWorkspace Operator is live on the dogfooding instance, verification should be done to ensure this...

Now that https://github.com/devfile/devworkspace-operator/pull/1251 & https://github.com/devfile/developer-images/pull/173 are merged, this issue seems to finally be resolved. Great work @dkwon17! 

> I think it stopped working recently because we have persistent home enabled and per-workspace persistent home was fixed recently: [devfile/devworkspace-operator#1241](https://github.com/devfile/devworkspace-operator/pull/1241) This is also what I believe caused this issue...

Thinking about the potential solutions @dkwon17 suggested: - Change the storagetype to `Ephemeral`: - Good easy workaround that can be accomplished by users quickly, however persistent storage is useful in...

@batleforc do you happen to have a reproducer devfile for this? Is there some specific configuration required for the endpoints? I apologize for taking so long to look into this...

I don't think this will be used to resolve this issue, but I figured it's worth mentioning: The DevWorkspaceOperatorConfig supports a default [devworkspace template spec](https://github.com/devfile/devworkspace-operator/blob/main/apis/controller/v1alpha1/devworkspaceoperatorconfig_types.go#L135-L138), that allows configuring components, commands,...