Windows docker stop命令挂起以移除陈旧容器

Windows docker stop命令挂起以移除陈旧容器,windows,docker,containers,azure-service-fabric,Windows,Docker,Containers,Azure Service Fabric,我有超过20个流动的容器,我想把它们移走。Docker stop命令挂起,没有输出。也尝试了docker rm命令,但它表示无法删除正在运行的容器。也尝试了docker容器修剪命令,但效果不佳。 这些是部署在服务结构群集上的windows容器。节点是windows server 2019核心(无GUI)。 节点上安装了docker和service fabric。由于安装了服务结构群集,docker引擎服务停止 1) docker stop container_ID-不工作 2) docker s

我有超过20个流动的容器,我想把它们移走。Docker stop命令挂起,没有输出。也尝试了docker rm命令,但它表示无法删除正在运行的容器。也尝试了docker容器修剪命令,但效果不佳。 这些是部署在服务结构群集上的windows容器。节点是windows server 2019核心(无GUI)。 节点上安装了docker和service fabric。由于安装了服务结构群集,docker引擎服务停止

1) docker stop container_ID-不工作

2) docker stop$(docker容器ls-aq)-不工作

3) 导航到C:\programdata\docker\windowsfilter并删除了容器

4) 在步骤3中,再次执行docker inspect已移除容器的容器id,并给出结果

5) 不知道如何移除这些重影容器

PS C:\ProgramData\docker\windowsfilter> docker version
Client: Docker Engine - Enterprise
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        f660560464
 Built:             07/25/2019 20:59:52
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Enterprise
 Engine:
  Version:          19.03.1
  API version:      1.40 (minimum version 1.24)
  Go version:       go1.12.5
  Git commit:       f660560464
  Built:            07/25/2019 20:57:41
  OS/Arch:          windows/amd64
  Experimental:     false

我应该能够移除这些我无法移除的陈旧容器。

试试docker rm-f$(docker ps-aq)也可以这样做。没有帮助。命令继续执行。我得到了一个“正在移除”。。但是什么也没发生。试试docker rm-f$(docker ps-aq)也能做到这一点。没有帮助。命令继续执行。我得到了一个“正在移除”。。但是什么也没发生。
PS C:\ProgramData\docker\windowsfilter> docker version
Client: Docker Engine - Enterprise
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        f660560464
 Built:             07/25/2019 20:59:52
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Enterprise
 Engine:
  Version:          19.03.1
  API version:      1.40 (minimum version 1.24)
  Go version:       go1.12.5
  Git commit:       f660560464
  Built:            07/25/2019 20:57:41
  OS/Arch:          windows/amd64
  Experimental:     false
PS C:\ProgramData\docker\windowsfilter> taskmgr
PS C:\ProgramData\docker\windowsfilter> docker info
Client:
 Debug Mode: false
 Plugins:
  cluster: Manage Docker clusters (Docker Inc., v1.0.1)

Server:
 Containers: 28
  Running: 28
  Paused: 0
  Stopped: 0
 Images: 4
 Server Version: 19.03.1
 Storage Driver: windowsfilter
  Windows:
 Logging Driver: json-file
 Plugins:
  Volume: local
  Network: ics l2bridge l2tunnel nat null overlay transparent
  Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
 Swarm: inactive
 Default Isolation: process
 Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
 Operating System: Windows Server Datacenter Version 1809 (OS Build 17763.678)
 OSType: windows
 Architecture: x86_64
 CPUs: 4
 Total Memory: 16GiB
 Name: nncsfc1000001
 ID: 73VB:NJAN:HXFN:R63P:DCSG:YCJT:K56A:F4MC:6NC5:KVUT:5J4C:MZ63
 Docker Root Dir: C:\ProgramData\docker
 Debug Mode: true
  File Descriptors: -1
  Goroutines: 202
  System Time: 2019-10-15T19:28:09.6416404Z
  EventsListeners: 1
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: API is accessible on http://localhost:2375 without encryption.
         Access to the remote API is equivalent to root access on the host. Refer
         to the 'Docker daemon attack surface' section in the documentation for
         more information: https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface