failed to shutdown container: failure in a Windows system call: The interface is unknown. (0x6b5)]
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- docker, go
调研方向
首先重现 mcr.microsoft.com/windows:ltsc2019 容器的关闭过程,并检查 Docker、Hyper-V 和 Windows Event 日志中的错误 0x800706B5。跟踪 hcsshim/libcontainerd 在 hcs::System::Shutdown 和 waitBackground 附近的关闭路径;完成的标准是确定原因,并防止容器因该错误而停止。
由索引模型根据 Issue 内容生成。
描述
For some time I'm facing strange Windows container (running mcr.microsoft.com/windows:ltsc2019) stops on three different machines.
Windows Event shows:
docker:
failed to shutdown container, and subsequent terminate also failed [container=ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a module=libcontainerd namespace=moby error=container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::waitBackground: failure in a Windows system call: The interface is unknown. (0x6b5)]
failed to shutdown container [namespace=moby container=ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a error=container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::Shutdown: failure in a Windows system call: The interface is unknown. (0x6b5)
[Event Detail: Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\vmhostedcontainerorchestrator.cpp(567)\vmcomputeagent.exe!00007FF60911BD91: (caller: 00007FF6090F81EC) Exception(740) tid(1504) 800706B5 The interface is unknown.
CallContext:[\Bridge_ProcessMessage\ComputeSystemManager_Shutdown\VmHostedContainer_Shutdown]
Provider: 00000000-0000-0000-0000-000000000000]: subsequent terminate failed container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::waitBackground: failure in a Windows system call: The interface is unknown. (0x6b5) process=init module=libcontainerd]
sending event [container=ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a event=exit event-info={ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a init 2520 4294967295 2023-05-09 20:55:20.6206041 +0200 CEST m=+107305.494057601 false failed to shutdown container: container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::Shutdown: failure in a Windows system call: The interface is unknown. (0x6b5)
[Event Detail: Provider: 00000000-0000-0000-0000-000000000000]
[Event Detail: onecore\vm\compute\management\orchestration\vmhostedcontainer\vmhostedcontainerorchestrator.cpp(567)\vmcomputeagent.exe!00007FF60911BD91: (caller: 00007FF6090F81EC) Exception(740) tid(1504) 800706B5 The interface is unknown.
CallContext:[\Bridge_ProcessMessage\ComputeSystemManager_Shutdown\VmHostedContainer_Shutdown]
Provider: 00000000-0000-0000-0000-000000000000]: subsequent terminate failed container ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a encountered an error during hcs::System::waitBackground: failure in a Windows system call: The interface is unknown. (0x6b5)} module=libcontainerd namespace=moby]
Immediately before that I see Hyper-V-VmSwitch, Hyper-V-Worker, Hyper-V-Compute messages:
[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Queue process notification 65536 / 0x00000000, process ID 2520
[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Query process notification, process ID 2520, result 0x00000000, notification 65536 / 0x00000000
NIC 96E4A63C-1656-4575-82A0-75A5574181B9--AC72BF8D-E1DC-4CCF-A3E9-A1CC0C7D58EC successfully disconnected from port .
The operation 'Delete' succeeded on nic 96E4A63C-1656-4575-82A0-75A5574181B9--AC72BF8D-E1DC-4CCF-A3E9-A1CC0C7D58EC (Friendly Name: ).
'ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a' was turned off. (Virtual machine ID 96E4A63C-1656-4575-82A0-75A5574181B9)
[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Queue system notification: 1 / 0x800706B5
[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Shut down compute system, result 0x800706B5
[ce28727851a80e47f95efb0052302bd0b5e3a99693e727ab4c8a79120462825a] Query compute system notification, result 0x00000000, notification 1 / 0x800706B5
It results as a stopped container. I'm able to manually start it again without any errors.
- 主要语言
- Go
- 星标
- 694
- 派生
- 304
- 平均合并
- 1 天 19 小时
- 30 天内合并 PR
- 28
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/hcsshim 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 42/100
-
难度 4/5 3-5 天 新手友好度 52/100
-
难度 3/5 1-2 天 新手友好度 68/100
-
难度 4/5 3-5 天 新手友好度 62/100
-
难度 4/5 3-5 天 新手友好度 58/100
查看 microsoft/hcsshim 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 65/100
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100
santhosh-tekuri/jsonschema#276 ·