Drive pool interfering with Docker for windows

[SootStack]

Hello,

Drive pool seems to be locking files as their created on drives that are not apart of the drive pool, its causing docker to fail to pull load any images. Is there anyway to limit drive pool from reading / locking files outside of the pool?

When I disable the drive pool service then Docker works correctly, and as soon as I start the "StableBit DrivePool Service" the problem immediately returns. 

 

docker version
Client:
 Version:      17.05.0-ce-rc1
 API version:  1.29
 Go version:   go1.7.5
 Git commit:   2878a85
 Built:        Tue Apr 11 20:55:05 2017
 OS/Arch:      windows/amd64


Server:
 Version:      17.05.0-ce-rc1
 API version:  1.29 (minimum version 1.24)
 Go version:   go1.7.5
 Git commit:   2878a85
 Built:        Tue Apr 11 20:55:05 2017
 OS/Arch:      windows/amd64
 Experimental: false

Drive Configuration

SSD Optimizer is running

500gb ssd: 
    windows volume -> C:\
    SSD cache volume (No drive letter assigned)

4x WD red 6tb disks (No drive letter assigned)
1x WD red 8tb disk (No drive letter assigned)

One Stable bit drive pool -> D:\
Made up of
    SSD cache
    4x WD red 6tb disks
    1x WD red 8tb disk

docker pull microsoft/nanoserver
Using default tag: latest
latest: Pulling from microsoft/nanoserver
bce2fbc256ea: Extracting [==================================================>]  252.7MB/252.7MB
6a43ac69611f: Download complete
failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage C:\ProgramData\Docker\windowsfilter\d4d43f11aa1cc5bbd0a1369bfc1af1491ab77c8d906a89efee5186f7a6b18084\UtilityVM: The process cannot access the file because it is being used by another process.

 

[SootStack]

To be blunt, based on what you've described, that shouldn't be happening at all.  Period. 

 

 

I agree, it was something I kept saying couldn't happen to myself as well. Yet 100% of the time when I shut down the service it worked, and 100% of the time I turned it on it failed.

I ran process monitor and I can confirmed your right, it does not ever specifically touch the files in C:\ProgramData\Docker\.

 

Further testing:

• When I remove the SSD cache volume and with the drive pool service running; I can no longer reproduce the issue.

now the weird bit. My hypothesis was that the issue would return.

• After re-adding the SSD cache volume to the drive pool with the drive pool service running. I am no longer able to replicate the issue, 
• I also tried rebooting and could no longer replicate the issue. 

[Christopher (Drashna)]

To be blunt, based on what you've described, that shouldn't be happening at all.  Period. 

 

Specifically, the only files that StableBit DrivePool should lock are: 

• Any files located in "C:\ProgramData\StableBit DrivePool" on the system that it's running on. 
• Any files located in the "PoolPart" folders on the pooled drives. 

Any files NOT in these locations should not be touched, let alone locked by StableBit DrivePool. Period. 

 

However, could you run the StableBit Troubleshooter:

http://dl.covecube.com/Troubleshooter/StableBit.Troubleshooter.exe

 

Also, it may be worth running "procmon" on the system to see what process is actually locking that file. 

[Christopher (Drashna)]

.... that's ... wow. 

 

So, apparently, the stars had to align or something here.  But I'm glad to hear that it sounds like this isn't happening any more.   Hopefully, the issue doesn't come back. Ever.