-
Notifications
You must be signed in to change notification settings - Fork 303
Closed
Labels
lifecycle/lockedlifecycle/stalerelated/windowsupdateMay be related to a windows updateMay be related to a windows updatestatus/triage
Description
- I have tried with the latest version of my channel (Stable or Edge)
- I have uploaded Diagnostics
- Diagnostics ID: C293FACB-C45E-482B-83F6-F4390B2C1A89/20190608143513
I have a zombie container after upgrading to Windows 1903. The container existed before the upgrade. After the upgrade Docker reports the container exists but any attempt to interact with or stop the container results in a "no such container" message or Docker simply hangs.
docker ps --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4c70fe356631 microsoft/mssql-server-windows-developer "powershell -Command…" 3 days ago Up 3 days (healthy) 0.0.0.0:1433->1433/tcp agitated_germain
docker exec -it agitated_germain powershell
no such container
docker exec -it 4c7 powershell
no such container
docker stop and docker rm -f hang indefinitely.
Information
- Windows Version: 1903
- Docker Desktop Version:
Client: Docker Engine - Community
Version: 19.03.0-beta3
API version: 1.40
Go version: go1.12.4
Git commit: c55e026
Built: Thu Apr 25 19:05:10 2019
OS/Arch: windows/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.0-beta3
API version: 1.40 (minimum version 1.24)
Go version: go1.12.4
Git commit: c55e026
Built: Thu Apr 25 19:06:34 2019
OS/Arch: windows/amd64
Experimental: true
Steps to reproduce the behavior
Not sure. Maybe get a copy of windows 1809, start a container, upgrade to 1903.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
lifecycle/lockedlifecycle/stalerelated/windowsupdateMay be related to a windows updateMay be related to a windows updatestatus/triage