ASP.NET layers not flagged as "foreign"

[sixeyed]

Seeking clarification on this. I build an image based on microsoft/aspnet:3.5-windowsservercore-10.0.14393.1715, tag it and push to a private registry. The two Windows Server base layers are not pushed (they're foreign layers), but the next three layers from the ASP.NET image are pushed. These total 3.7GB:

In the ASP.NET image the 3.5 framework is added from a local CAB, so users can't reproduce those layers for themselves. Should they also be flagged as foreign layers so users aren't pushing them to their own registries?

[shirhatti]

Duly noted and definitely worth exploring.
I'm not familiar with what the guidance is for whether something should be marked as a foreign layer or not. Is this something that's already well defined?

[HongGit]

@richlander any thoughts?

[MichaelSimons]

My understanding is the Windows OS layers are foreign layers because the Windows licensing requires them to be hosted by Microsoft servers. The .NET products do not have these constraints therefore they are contained in "normal" layers and can be hosted on any registry.

[HongGit]

@sixeyed hope this answers your question.