moby: what does exitCode=3221226505 means when container die?
Description
When run the following commands, the docker container will run for a while and then exit with errorcode 3221226505.
docker run -it mcr.microsoft.com/windows/servercore:ltsc2019 cmd
Steps to reproduce the issue:
- Check for update and install the latest update on Windows Server 2019. After that, the build number of the Server OS should be 10.0.17763.914.
- Update Docker to latest version of 18.09.11, includes the client and server.
- Run the commands from a elevated PowerShell cmd window to run docker container: docker run -it mcr.microsoft.com/windows/servercore:ltsc2019 cmd
Describe the results you received: The docker container will run for several minutes. Finally it will exit automatically with errorcode 3221226505.
Describe the results you expected: The docker container should run as long as possible until i stop it.
Additional information you deem important (e.g. issue happens only occasionally):
It happens 100% on our machine.
Output of docker version
:
Client: Docker Engine - Enterprise
Version: 18.09.11
API version: 1.39
Go version: go1.12.12
Git commit: 6112046bc9
Built: 11/13/2019 07:51:12
OS/Arch: windows/amd64
Experimental: false
Server: Docker Engine - Enterprise
Engine:
Version: 18.09.11
API version: 1.39 (minimum version 1.24)
Go version: go1.12.12
Git commit: 6112046bc9
Built: 11/13/2019 07:49:53
OS/Arch: windows/amd64
Experimental: false
Output of docker info
:
Containers: 3
Running: 0
Paused: 0
Stopped: 3
Images: 1
Server Version: 18.09.11
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd 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 2019 Standard Version 1809 (OS Build 17763.914)
OSType: windows
Architecture: x86_64
CPUs: 14
Total Memory: 16GiB
Name: ABC
ID: L7OT:ZC43:7OGX:3APB:FHFA:AEQ7:CYM6:OZ7V:XYKT:KRKW:4HOF:XFHT
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.): Windows Server 2019 VM
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 64 (6 by maintainers)
I can confirm that updating the VMware tools to 11.0.6 fixes the issue!
Finally a glimpse of light… i will test it aswell
Update: Installed VMWareTools 10346 and it is working now.
no we’re not using fusion pro 11. yeah it’s esxi6.7 I believe. On the up side, i downgraded vmware tools (https://docs.vmware.com/en/VMware-Tools/index.html) on one of our problematic VM’s from 11.0 back to 10.1 and the problems gone away. Containers are back running > 1hr 😃 😃
Downgrading the VMTools to 10.3 fixed the issue for us as well.
@simmohall, you are right. The same issue has been resolved by degrading VMTools. https://github.com/docker/for-win/issues/5044