microsoft / microsoft/Windows-Containers
Windows pod stuck in terminating state with subpath in volumemounts
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 551
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I don't want to double post, this bug has already been reported in the AKS Github:
Windows pod stuck in terminating state with subpath in volumemounts
I am working on escalating this through Azure support, but it's taking ages - and effort - to get through the first line of support. This issue only affects windows containers, but it is unclear what part of the stack is responsible for the issue.
I'm hoping that posting here will give it some visiblity or ping the right people at MS.
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
The report identifies Windows containers, Kubernetes-style volume mounts with subpaths, and an existing AKS issue, but names no repository files, tests, or entry point. Start by comparing the linked AKS report and determining which layer owns the terminating-state behavior; the payload does not define a concrete fix or completion test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, kubernetes
- Domain
- cloud, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100