Need 2019 and 2022 4.8 dockerimages with latest service and vulnerability patch update #658

Activity

1. pillaiarc

   added

   questionFurther information is requestedFurther information is requested

   triageNew and needs attentionNew and needs attention

   on Oct 21, 2026
2. github-actions commented on Oct 21, 2026

   

   github-actionsBot

   on Oct 21, 2026 – with GitHub Actions

   More actions

   Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.
3. smiezah-msft commented on Oct 21, 2026

   

   smiezah-msft

   on Oct 21, 2026

   Last edited by smiezah-msft

   Collaborator

   More actions

   Hi pillaiarc, thanks for the details! To make sure we're understanding the scenario correctly, could you also provide the Windows version/build of the container host, the container runtime/orchestrator you're using, and whether these containers run with process or Hyper-V isolation?

   For the container image itself, the currently published supported .NET Framework runtime combinations include .NET Framework 4.8 on Server Core LTSC 2019 and .NET Framework 4.8.1 on Server Core LTSC 2022 and LTSC 2025. Microsoft also notes that .NET Framework 4.8 and 4.8.1 can run apps built targeting any version of .NET Framework 4 (see the .NET Framework runtime image README). Could you clarify whether your application merely targets 4.8, or whether its support policy requires the installed runtime to remain exactly 4.8?

   One additional consideration is base image lifecycle. Server Core LTSC 2019 is already out of mainstream support, although it remains in extended support through January 9, 2029 and continues to receive applicable servicing. LTSC 2022's mainstream support also ended on October 13, 2026 (extended support runs through October 14, 2031), while LTSC 2025 remains in mainstream support through October 9, 2029 (see Base image servicing lifecycles). For a new or forward-looking configuration, we recommend planning migration to a newer Windows Server base rather than establishing a new dependency on LTSC 2019, however, perhaps you can also clarify your specific use of Server Core LTSC 2019?

   If your application can run on the 4.8.1 runtime, the supported .NET Framework 4.8.1 images would therefore be the preferred direction: LTSC 2022 is closest to what you described, and LTSC 2025 offers the longest support runway. If you require exactly 4.8 on LTSC 2022, please confirm that requirement and the host/isolation information above so we can evaluate that scenario more specifically.
4. pillaiarc commented on Oct 23, 2026

   

   pillaiarc

   on Oct 23, 2026

   Author

   More actions

   The docker host is 2019 and 2022 Host, container runtime is moby/docker https://github.com/moby/moby and we are using containes un with pocess (not with HyperV isolation)
   Our offer targets 4.8 we we have always tested with 4.8 and never with 4.8.1 hence wanted to know earlier mcr used to have 4.8 2019 , 2022 available but is not available from last 1-2 months.

   We use LTSC 2019, 2022 as most of our customers are still on that.

   So our application needs 3 things

   1. 4.8 .net framework
   2. .Net 10.0x runtime
   3. Windows DCOM support

   The main challenge is 4.8 .net framework related patches are only available through these images and we cant patch container without rebuilding. hence we need 2019 and 2022 images