Problem when a directory attached to the host system is renamed

Docker Desktop for Mac
1

Expected behavior

Example container with a mount point equal to /var/xxx

cd /var/xxx
mkdir mydir
touch bb
cd …
mv mydir mynewdir
cd mynewdir
ls

Actual behavior

cd /var/xxx
mkdir mydir
touch bb
cd …
mv mydir mynewdir
cd mynewdir
ls

ls: cannot access bb: No such file or directory
bb

Information

Container is using ubuntu 15.10

pinata diagnose -u
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta12
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160525-192401.tar.gz
Most specific failure is: No error was detected
Your unique id is: D6E838C4-C5B2-42E8-9532-9E1FD89C4A50
Please quote this in all correspondence.

Steps to reproduce the behavior

Described above

On a local filesystem (/tmp for example) the problem doesn’t exist.
Seems to be in strong relationship with the “mv” command

Very inconvenient for my project

2

Sorry bad testcase

You shoud read:

mkdir mydir
cd mydir
touch bb
…

3

In the configuration with a VIRTUALBOX VM, works properly.

4

On the host file system, the file is accessible normally, not in the container. Even if the container is stopped and restarted, the file is always not accessible.

5

If the directory “mynewdir” is renamed back to “mydir”, the file “bb” becomes accessible …

6

Workaround:

cd /var/xxx
mkdir mydir
cd mydir
touch bb
cd …
mv mydir /tmp
mv /tmp/mydir mynewdir
cd mynewdir
ls

Here the result is as expected. But not very useful if “mydir” is a big directory.

7

Problem solved in the last beta delivered (1.11.1-beta13)