Sometimes It is necessary to have same HOME for plugin and dev containers

[svor]

In some cases it is necessary to have the same value of HOME env for both containers: dev container and plugin container.

For example it is necessary for dotnet workspace, which uses omnisharp remote plugin. In this case both containers want to build the project (or sample) and the build process rewrites project's configuration which describes where dependency packages are located. And usually for dotnet the folder with that packages locates in $HOME/.nuget directory. It means that the value of dependency is different for these containers.

Probably it makes sense to have the same value of $HOME variable (maybe also for some another ENVs) for all containers.

[tsmaeder]

Another instance of the "plugins assume they are on the same machine" problem. @svor can we get the two tools to use the $HOME variable instead of a fixed path?

[svor]

@tsmaeder at the moment I don't know how to do that in case with dotnet, maybe it is possible to provide some parameter for build command...

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

[tsmaeder]

lifecycle/frozen