Stay organized with collections
Save and categorize content based on your preferences.
Issues with Windows IIS services migration
This document describes workarounds for some issues that you might
encounter while migrating Windows IIS services.
Windows IIS deployment marked not ready
The deployment of Windows IIS workloads might be marked as not ready due
to short timeouts. If you're deploying your workloads using Skaffold, then
the deployment might show as failed.
As a workaround for this issue, increase the readiness probe timeout and
period using PowerShell:
Skaffold build for Windows images might fail on a Windows machine because
Skaffold tries to pull the base image for the wrong target.
If this issue occurs, you might see an error message similar to the following
message:
Checking cache...
- migrated-image-6jc3z: Error checking cache.
getting hash for artifact "migrated-image-6jc3z": getting dependencies for "migrated-image-6jc3z": parsing ONBUILD instructions: retrieving image "mcr.microsoft.com/dotnet/framework/aspnet:4.8": no child with platform linux/amd64 in index mcr.microsoft.com/dotnet/framework/aspnet:4.8
As a workaround for this issue, pull the image manually using the docker pull
command, and run the Skaffold build again.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Issues with Windows IIS services migration\n==========================================\n\nThis document describes workarounds for some issues that you might\nencounter while migrating Windows IIS services.\n\nWindows IIS deployment marked not ready\n---------------------------------------\n\nThe deployment of Windows IIS workloads might be marked as not ready due\nto short timeouts. If you're deploying your workloads using Skaffold, then\nthe deployment might show as failed.\n\nAs a workaround for this issue, increase the readiness probe timeout and\nperiod using PowerShell: \n\n foreach ($file in (Get-ChildItem . -Recurse -Include \"deployment_spec.yaml\")) { (Get-Content $file).replace(\"periodSeconds: 10\", \"periodSe\n conds: 30\").replace(\"timeoutSeconds: 1\", \"timeoutSeconds: 10\") | Set-Content $file }\n\nSkaffold build for Windows images fails\n---------------------------------------\n\nSkaffold build for Windows images might fail on a Windows machine because\nSkaffold tries to pull the base image for the wrong target.\n\nIf this issue occurs, you might see an error message similar to the following\nmessage: \n\n Checking cache...\n - migrated-image-6jc3z: Error checking cache.\n getting hash for artifact \"migrated-image-6jc3z\": getting dependencies for \"migrated-image-6jc3z\": parsing ONBUILD instructions: retrieving image \"mcr.microsoft.com/dotnet/framework/aspnet:4.8\": no child with platform linux/amd64 in index mcr.microsoft.com/dotnet/framework/aspnet:4.8\n\nAs a workaround for this issue, pull the image manually using the `docker pull`\ncommand, and run the Skaffold build again."]]
