Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

get an error when do 'docker run': C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: hcsshim::PrepareLayer - failed failed in Win32: The device is not ready. (0x15).

Open
  • Is something wrong?
#1,425 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, go
Domain
devops, operating-systems

Research direction

Start with the reported docker info output and the hcsshim::PrepareLayer error on Windows Server 2019, then trace the relevant hcsshim handling for this failure. Done would require identifying the resource or subsystem involved and establishing whether a fix is possible without restarting the Docker engine; the issue names no source file or test.

Written by the indexing model from the issue text.

Description

I had run over 200 containers on my windows server 2019, and when I try to run a new docker on the same computer I get a error :

C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: hcsshim::PrepareLayer - failed failed in Win32: The device is not ready. (0x15).
It's my first time see this error. I want to solve it and know what leads this problem. I did some Google things, and find few information, somebody say it means resource exhausted? But there is enough CPU and Mem resource on my computer, or what kind of resource it mean?

Does anybody know how to fix this problem without restart docker engine? Because I had run 200+ container and I wan't let them down.

there is some information about my enviroment:

PS C:\Users\Administrator> docker info
Client:
 Debug Mode: false

Server:
 Containers: 269
  Running: 265
  Paused: 0
  Stopped: 4
 Images: 36
 Server Version: 19.03.8
 Storage Driver: windowsfilter
  Windows:
 Logging Driver: json-file
 Plugins:
  Volume: local
  Network: ics internal l2bridge l2tunnel nat null overlay private 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 2019 Datacenter Version 1809 (OS Build 17763.1339)
 OSType: windows
 Architecture: x86_64
 CPUs: 56
 Total Memory: 223.9GiB
 Name: WIN-V6RDFC35B6C
 ID: B6OV:VPRQ:DTGO:Z6JG:2U7G:QUCI:XFWQ:EVOI:FJKA:DSMO:FXUC:URCA
 Docker Root Dir: D:\ProgramData\Docker
 Debug Mode: true
  File Descriptors: -1
  Goroutines: 1878
  System Time: 2022-06-09T14:32:06.6242483+08:00
  EventsListeners: 2
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine�
Dominant language
Go
Stars
694
Forks
304
Avg merge
1d 22h
Merged PRs (30d)
31

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/hcsshim

All issues in microsoft/hcsshim

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.