docker-compose.yml: remove volume declaration

[rjw57]

When using docker-machine as recommended in the README file, the
instructions for getting started do not work since the web application
container fails to start.

That's because the default "local" driver for Docker volumes doesn't
work directly with docker-machine (see [1] for a discussion of this).

The existing Dockerfile already copies the web application files to the
container and removing the volume configuration allows the web
application to start. Database migration and initial user creation can
then be performed. If the volume configuration is kept, the
manage.py script cannot be found because the /code directory
appears to be empty.

The downside of this change is that changes to the local files will not
be reflected until a docker-compose build web command is issued.
Depending on how a local developer prefers to work, this may lead to
confusion.

[1] https://alexanderzeitler.com/articles/docker-machine-and-docker-compose-developer-workflows/

[envycontent]

I've tried this out - as a complete newbie using the docker option and it worked fine. Would help to have the additional step (docker-compose build web) in the readme as well.

[rjw57]

Good point. I added a few lines to the README in c33f390

[ahaith]

Hi Rich, Thanks for the PR. The steps as described for us work fine. i.e. the code directory is mounted successfully and any changes made on the host are immediately reflected within the container. The server restarts automatically whenever code changes.

Hopefully we can figure out why the mounting isn't working for you, and update the ReadMe with some relevant guidance.

We are all using OSX, and are running our containers on a local vm created by docker-machine create --driver=virtualbox default. N.B. the 'local' volume driver for Mac only works for files in /Users. All of our repos are therefore located within our home directories.

[rjw57]

I'm using docker-machine with Virtualbox driver under Linux.

Doing some more digging, it appears that local volumes with Virtualbox don't work well on Linux. See docker/machine#1376 and https://github.com/boot2docker/boot2docker/#virtualbox-guest-additions specifically:

In case it isn't already clear, the Linux host support here is currently hazy. You can share your /home or /home/jsmith directory as Users or one of the other supported automount locations listed above, but note that you will then need to manually convert your docker run -v /home/...:... bind-mount host paths accordingly (ie, docker run -v /Users/...:...). As noted in the previous paragraph however, this is likely to change in the future as soon as a more suitable/scalable solution is found and implemented.

Looks like one might need to add a note in the README about this and perhaps link to the PR as a workaround?

[Mellysoe02]

test