Unable to move files in volume directory in Windows docker container

[dtretyakov]

Expected behavior

File move succeeds.

Actual behavior

File move fails with Access is denied.

Information

Diagnostic ID : F74EE66C-752F-4676-B9C3-2D44D291D24C/2017-09-01_19-21-39
Dockerfile:

FROM microsoft/nanoserver
VOLUME c:/volume

Steps to reproduce the behavior

1. Create a new image based on microsoft/nanoserver / microsoft/windowsservercore with volume
2. Run it docker run -it -v C:\Users\User\Documents\volume:c:/volume volume-nanoserver powershell
3. Create a file and try to rename/move:

PS C:\volume> Move-Item file.txt file2.txt
Move-Item : Access to the path is denied.
At line:1 char:1
+ Move-Item file.txt file2.txt
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (C:\volume\file.txt:FileInfo) [Move-Item], UnauthorizedAccessException
    + FullyQualifiedErrorId : MoveFileInfoItemUnauthorizedAccessError,Microsoft.PowerShell.Commands.MoveItemCommand

In non volume directory move succeeds.

[Crevax]

What permissions do you have on the folder? I was running into the same issue until I gave Modify access to the Authenticated Users principal.

[dtretyakov]

Hi, I use default permissions for everything, dockerd service is running under LocalSystem account, this folder was created under the User account. I could not find anything regarding specific access settings for Authenticated Users in docker documentation.

[Crevax]

I'll be first to admit I'm not a Windows security/system expert, so maybe using Authenticated Users isn't the correct Principal (and I'm using the term Principal since that's what's used when setting folder permissions since it's not restricted to just User assignment). Regardless, I think the issue you're coming across is still due to your folder's permissions.

Since the folder was created by your User account (and the folder is in your user's specific directory), your Container's user probably doesn't have the right permissions to move the file.

When I was running into the same issue, I could make files and folders within the mounted volume. So it was weird that moving/renaming files was forbidden. But again I'm not an expert on how that's handled in Windows. Maybe someone with more knowledge in that regard can chime in. I wasn't able to find anything around permissions for mounting volumes in a Windows container either. I just know relaxing the permissions on my folder solved the issue for me.

I just chose Authenticated Users after duplicating the setup in a different folder, checked that everything worked there, and looked at the different permissions. Hope that helps clear things up!

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[dtretyakov]

/lifecycle frozen

[GCSBOSS]

I have the same problem with stable version.

[JeffCyr]

I don't know if it's the same issue but I had a similar problem with Docker for Windows 19.03.1 on Windows 10 1903. I could create/edit/delete files in a volume but I could not rename or move the file, it gave the error "DirectoryNotFound". The same operation was possible outside the volume.

I recreated the container and the issue was gone, I'm not sure how to reproduce

[spinico]

Also similar issue for me, but in my case I had the File Server Resource Manager (Windows Feature) installed on the Windows Server host which caused problem to move files in a volume within a container. I had to uninstall the mentioned feature to make it work again.

[JeffCyr]

Related issue: moby/moby#38256

[Andrysky]

hi have any news?