Document Details

Tutorial Custom Container
Home / Scan #41 / Tutorial Custom Container
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation is structured with a clear separation between Windows and Linux via pivots, but the Windows section is presented first and is significantly more prescriptive and tool-specific. The Windows tutorial relies heavily on Visual Studio, Windows Explorer, and PowerShell scripts, with no mention of equivalent Linux workflows or cross-platform alternatives. The Linux section, by contrast, uses generic CLI and Docker commands, but the Windows section lacks any Linux or cross-platform guidance for users who may be developing on non-Windows systems. There is also a lack of parity in the depth of explanation for certain steps (e.g., font installation and orchestration support are only covered for Windows).
Recommendations
  • Provide cross-platform alternatives in the Windows section, such as how to build and deploy custom containers using the .NET CLI and Docker commands instead of Visual Studio and Windows Explorer.
  • Include Linux-based examples for tasks like font installation (e.g., using RUN commands in the Dockerfile to install fonts on Linux images) to mirror the Windows example.
  • Avoid assuming the use of Windows-specific tools (Visual Studio, Windows Explorer, PowerShell) as the only workflow; mention VS Code, JetBrains Rider, or CLI-based approaches where possible.
  • Reorder or clarify the pivots so that neither Windows nor Linux is implicitly prioritized, or explicitly state that both are equally supported.
  • Where PowerShell scripts are referenced, provide Bash or shell script equivalents for Linux users.
  • Ensure that all major steps (such as adding orchestration support, configuring the Dockerfile, and publishing to Azure Container Registry) have both Windows and Linux instructions, or at least cross-references.
  • Add a summary table at the top comparing the Windows and Linux workflows, highlighting tool differences and parity.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-12 00:58 #8 cancelled Clean Clean
2025-07-10 05:06 #7 processing Clean Clean
2025-07-09 23:22 #6 cancelled Clean Clean

Flagged Code Snippets

FROM mcr.microsoft.com/dotnet/framework/aspnet:4.7.2-windowsservercore-ltsc2019

RUN ${source:-obj/Docker/publish/InstallFont.ps1}

14/09/2018 23:16:19.889 INFO - Site: fonts-win-container - Creating container for image: customfontsample20180914115836.azurecr.io/customfontsample:latest.
14/09/2018 23:16:19.928 INFO - Site: fonts-win-container - Create container for image: customfontsample20180914115836.azurecr.io/customfontsample:latest succeeded. Container Id 329ecfedbe370f1d99857da7352a7633366b878607994ff1334461e44e6f5418
14/09/2018 23:17:23.405 INFO - Site: fonts-win-container - Start container succeeded. Container: 329ecfedbe370f1d99857da7352a7633366b878607994ff1334461e44e6f5418
14/09/2018 23:17:28.637 INFO - Site: fonts-win-container - Container ready
14/09/2018 23:17:28.637 INFO - Site: fonts-win-container - Configuring container
14/09/2018 23:18:03.823 INFO - Site: fonts-win-container - Container ready
14/09/2018 23:18:03.823 INFO - Site: fonts-win-container - Container start-up and configuration completed successfully