Issue with modifying files in volumes

[zerok]

Hi 😊

We have run into a bit of a problem after upgrading to Docker 1.11 (also on new installations) where modifications of files inside a volume misbehave. Here is what we've tried:

• Creating a new file inside the volume works from within the container -> OK
• Deleting a file outside the container results in the file no longer being visible inside the container -> OK
• Modifying an existing file from inside the container works but is only visible outside of the container -> BAD
• Modifications made to an existing file outside the container are not visible inside the container -> BAD

Tested with:

• docker-machine 0.7.0
• docker 1.11.0, build 4dc5990
• OSX 10.11.4
• VirtualBox 5.0.16 r105871

Everything works as expected when doing these operations using Docker for Mac (Version 1.11.0-beta7 (build: 5830) 8b45bc3afc0ca2363890032ac63b003d80ccc242) or on a Linux host without docker-machine.

The Docker file we've used to reproduce this looks like this:

FROM alpine

but we initially noticed this while using the official nginx image using jessie, hence we started to suspect it not being related to the used image.

After restarting the docker-machine it looks like a sync or flush takes places that changes the state of the volume again.

We have tried to provide a test case for reproducing part of this issue. For this purpose I've created a gist: https://gist.github.com/zerok/79ba3842a475bb2d68b0c6767dc31781 with Dockerfile, test script and test-data.

Thank you for your help 🙂 I hope this is the correct project to report this issue. In the end I'm not sure if it is docker-machine or boot2docker, but as it works with Docker for Mac I kind of assumed it was more a docker-machine issue 😔

[thatnerdjosh]

+1 I noticed the same thing, when using volumes in docker-compose it doesn't use latest files from local machine

[thatnerdjosh]

Looks like the docker container sees the changes properly, but the machine hosting the containers does not, really odd that it doesn't work if the container sees the file changes, but then again there is probably a lot going on with how docker containers see files :)

[nathanleclaire]

Thanks for the issue @NerdsvilleCEO @zerok, I'll take a look.

[p7k]

+1

[Zacmatix]

+1