Need option to optimize NuGetFallbackFolder contents for Docker/build server scenarios

[MichaelSimons]

When defining a Dockerfile intended to be used for building .NET Core apps, it is useful to have the canonical NuGet packages cached on disk in order to avoid having to re-pull them each time the image is used. The same applies when setting up a build server machine/VM. For both of these scenarios it is important to not bloat the resulting image with content that would never be used.

If you browse the NuGetFallbackFolder today you will notice the majority of the content is not applicable Docker/build server scenarios.

It would be ideal if there was an option to trim out all unneeded files from the package folders. A bare minimum would be to honor the NUGET_XMLDOC_MODE=skip environment variable setting by the first run experience.

Note: The NUGET_XMLDOC_MODE=skip setting used to be honored by the first run experience prior to the introduction of the NuGetFallbackFolder.

Related to dotnet/dotnet-docker#237

cc @richlander, @natemcmaster, @glennc

[richlander]

This is similar to the portable SDK concept that I've talked about. This would be valuable for more than just Docker.

[natemcmaster]

I've just added a change to aspnetcore 2.1.3 to produce an artifact that includes the same contents as the NuGetFallbackFolder, but without the xmldoc files and .nupkg files. This saves >800 MB of space. We started producing this artifact for Azure Web Apps, but it could be reused generally. What do you think about having Docker consume this artifact instead of the bigger .lzma in a 2.1 patch?

[github-actions]

Due to lack of recent activity, this issue has been labeled as 'stale'. It will be closed if no further activity occurs within 30 more days. Any new comment will remove the label.

[github-actions]

This issue will now be closed since it has been labeled 'stale' without activity for 30 days.