Summary
We build a Windows container image FROM mcr.microsoft.com/windows/servercore:ltsc2019 that installs and runs the Azure Data Factory Self-Hosted Integration Runtime (SHIR), based on Microsoft's reference sample (Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container).
An image built while the base resolved to 10.0.17763.8511 works — the SHIR node registers and reports Online in Data Factory. An image built while the base resolved to 10.0.17763.9020 does not — the SHIR node does not come online. The Dockerfile, scripts, and SHIR installer are unchanged between the two builds; the base OS build is the only difference.
We have not determined the underlying cause and are not attributing it to any specific component — reporting the observed difference in case it is a known change or expected behavior.
Environment
|
Value |
| Base image |
mcr.microsoft.com/windows/servercore:ltsc2019 |
| Base build where it works |
10.0.17763.8511 (KB5078752) |
| Base build where it does not work |
10.0.17763.9020 (KB5099538) |
| Host |
Azure App Service for Containers (Windows) |
| Workload |
Azure Data Factory Self-Hosted Integration Runtime, installed via IntegrationRuntime.latest.msi |
Observed behavior
- Image built on base 17763.8511 → SHIR node registers and shows Online.
- Image built on base 17763.9020 (identical Dockerfile, scripts, and SHIR installer) → SHIR node does not come online.
Steps to reproduce
- Build a Windows container image
FROM mcr.microsoft.com/windows/servercore:ltsc2019 that installs IntegrationRuntime.latest.msi and registers a SHIR node (per the reference sample above).
- Run it with a valid SHIR auth key on base build 17763.9020 and observe the node does not come online.
- Build the identical image on base build 17763.8511 and observe the node comes online.
Notes
Happy to provide container logs or any other details on request.
Summary
We build a Windows container image
FROM mcr.microsoft.com/windows/servercore:ltsc2019that installs and runs the Azure Data Factory Self-Hosted Integration Runtime (SHIR), based on Microsoft's reference sample (Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container).An image built while the base resolved to 10.0.17763.8511 works — the SHIR node registers and reports Online in Data Factory. An image built while the base resolved to 10.0.17763.9020 does not — the SHIR node does not come online. The Dockerfile, scripts, and SHIR installer are unchanged between the two builds; the base OS build is the only difference.
We have not determined the underlying cause and are not attributing it to any specific component — reporting the observed difference in case it is a known change or expected behavior.
Environment
mcr.microsoft.com/windows/servercore:ltsc201910.0.17763.8511(KB5078752)10.0.17763.9020(KB5099538)IntegrationRuntime.latest.msiObserved behavior
Steps to reproduce
FROM mcr.microsoft.com/windows/servercore:ltsc2019that installsIntegrationRuntime.latest.msiand registers a SHIR node (per the reference sample above).Notes
Happy to provide container logs or any other details on request.