chown has no affect for mounted volumes

[ptrewhella]

Expected behavior

Directory owner can be changed with chown within the container for mounted volumes.

Actual behavior

Using chown within the container for a mounted volume does nothing.

Information

• Diagnostic ID from "Diagnose & Feedback" in the menu.
• Windows 10 Pro, Docker 1.12.0-beta21 (build 5971) - also tried stable release

Steps to reproduce the behavior

1. C:\Users\sotera>docker run --rm -v c:\users\sotera\docker\sotera:/var/lib/postgresql/data postgres /bin/bash -c "chown postgres:postgres /var/lib/postgresql/data && ls -lh /var/lib/postgresql/"

   total 4.0K drwxr-xr-x 2 root root 4.0K Aug 16 23:29 data

[ptrewhella]

Here is a similar command executed on my Mac. Notice the owner is changed to postgres:postgres.

iridium:rt ptrewhella$ docker run --rm -v /Users/ptrewhella/data:/var/lib/postgresql/data postgres /bin/bash -c "chown postgres:postgres /var/lib/postgresql/data && ls -lh /var/lib/postgresql"

total 512 drwxr-xr-x 2 postgres postgres 68 Aug 17 00:23 data iridium:rt ptrewhella$

[ptrewhella]

This behavior renders the PostgreSQL container pretty much useless on a Windows host, because it will not run as user root, and it will not run unless the user under which the process is running owns the files.

[dgageot]

@ptrewhella I haven't tried it but Beta25 brings some changes to the file mounting. There's a slight chance that it might help. Could you give it a try?

[ptrewhella]

@dgageot Yes, sure I'll try it now. Thanks.

[ptrewhella]

@dgageot Just updated and ended up with the same results (root:root) after chown.

[otravers]

I can replicate this behavior as of Docker for Windows 1.12.1-stable (b7135). I tried Chowning via docker exec, and via bash.

[sameronline]

I still can replicate this behavior on 1.12.5 (9503) stable