redhat-developer/s2i-aspnet-musicstore-ex doesn't build on openshift. ``` /opt/app-root/src/.nuget/packages/Pomelo.JsonObject/1.1.0/src/Pomelo.JsonObject/System/JsonObject.cs(4,29): error CS0436: The type 'JsonObject<T>' in '/opt/app-root/src/.nuget/packages/Pomelo.JsonObject/1.1.0/src/Pomelo.JsonObject/System/JsonObject`1.cs' conflicts with the imported type 'JsonObject<T>' in 'Pomelo.JsonObject, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in '/opt/app-root/src/.nuget/packages/Pomelo.JsonObject/1.1.0/src/Pomelo.JsonObject/System/JsonObject`1.cs'. ``` The referenced Pomelo.JsonObject contains dlls and source code. Because the .nuget folder is under the project folder, the compiler thinks it should also compile this code. Then it ends up with duplicate types: one from the dll and one from the source code. The .nuget folder gets put there because the Dockerfile sets HOME=/opt/app-root/src. HOME and src must be distinct folders.
This is a variant of bug 1384151. We can fix nupkgs shipped with .NET Core itself, but we have no control over those downloaded from nuget.org. I suspect we have to modify things so that $HOME is not the same as the source root (/opt/app-root/src) and is not under the source root.
> I suspect we have to modify things so that $HOME is not the same as the source > root (/opt/app-root/src) and is not under the source root. Exactly!
(In reply to Omair Majid from comment #1) > I suspect we have to modify things so that $HOME is not the same as the > source root (/opt/app-root/src) and is not under the source root. Agreed. I was meaning to create an upstream issue for this.
Testsuite passed for both 1.0.4 and 1.1.1 1.0.4 https://bugzilla.redhat.com/show_bug.cgi?id=1430300#c4 1.1.1 https://bugzilla.redhat.com/show_bug.cgi?id=1430310#c4
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0560