我在Windows Server 2016 VM上进行了设置泊坞窗。我们有docker Dev，Test和Prod环境，最近我们在Prod中观察到一些奇怪的错误。
下面列出了docker info的输出。
PS C:\Windows\system32> docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 4
Server Version: 17.06.2-ee-15
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd json-file logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 14393 (14393.2551.amd64fre.rs1_release.181004-1309)
Operating System: Windows Server 2016 Standard
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 1.704GiB
Name: ntprnch01
ID: F2WP:CY45:XBIU:3FE4:BUBS:Z467:SVQ7:3HZB:GUB5:KWWJ:7H2Y:FFLA
Docker Root Dir: D:\docker
Debug Mode (client): false
Debug Mode (server): false
Http Proxy: http://proxydetails [Edited]
Https Proxy: http://proxydetails [Edited]
No Proxy: Noproxy List[Edited]
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
Provaterepo.company:9000
127.0.0.0/8
Live Restore Enabled: false
我还没有在这个特定的盒子中运行任何容器。 但是我下载了一些docker镜像。我几周前做了docker设置，今天当我查看事件日志时，我惊讶地发现很少有docker错误。
想知道在事件日志中可能导致这些错误的原因。但是，是的，当我现在尝试导入新图像时，不会记录任何错误。 这些错误不断发生。总体内容保持不变，但是容器ID不断变化。
错误是
The description for Event ID 1 from source docker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Handler for POST /v1.24/containers/bca4617b67f1e227ccc702b9b097586f68470abae258b653dfd1a7bd1c1d270d/kill returned error: Cannot kill container bca4617b67f1e227ccc702b9b097586f68470abae258b653dfd1a7bd1c1d270d: Container bca4617b67f1e227ccc702b9b097586f68470abae258b653dfd1a7bd1c1d270d is not running