microsoft / microsoft/Windows-Containers
Docker Build Timeout Issue For Untrusted Workload
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 551
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Please fill out all the sections below for bug issues, otherwise it'll be closed as it won't be actionable for us to address.
Describe the bug
Docker build timeout issue sometimes happened in SqlTools Untrusted workload initialization. The timeout is 5 mins. In .dockerfile, it needs to run PowerShell script to install .NET 8 SDK first and then run CMD command. It always completed .NET8 SDK installation but hang in CMD step (I will share the required files in "To Reproduce").
"Done unzipping contents of C:\SqlToolsCore.Untrusted\dotnet-sdk.zip to C:\Program Files\dotnet-sdk" is the log meaning that it completed SDK installation. But it never went to CMD
To Reproduce
Steps to reproduce the behavior:
There are the scripts in untrusted workload:
docker file
install SDK script
This is the install docker script:
InstallDocker.ps1
workloadbase-windowsservercore-untrusted.dockerfile
Expected behavior
Docker build should complete within 5 minutes.
Configuration:
- Edition: WindowsServerCore
- Base Image being used: mcr.microsoft.com/windows/server:ltsc2022
- Container engine: [docker]
- Container Engine version [22]
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with SqlToolsCore.Untrusted.dockerfile and Scripts/install_sdks.ps1, then inspect InstallDocker.ps1 and workloadbase-windowsservercore-untrusted.dockerfile from the linked repositories. Reproduce with Windows Server Core, the ltsc2022 base image, Docker 22, and the five-minute timeout, focusing on the transition after the .NET 8 SDK installation log. Done means the build reliably reaches the CMD step and completes within five minutes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, powershell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100