Enable developers using Windows to run the backend Docker container locally

[MikeTheCanuck]

We have at least two developers on the Budget team who are using Windows machines for local development work.

When @mxmoss (using Windows 10 + Docker Toolbox for Windows) tried to run docker-compose up from the current "dockerize" branch of this project, he encountered this error:

moss@DESKTOP-9LE20OE MINGW64 /c/develop/python/team-budget/budget_proj (dockerize)
$ docker-compose up
Starting budgetproj_web_1

ERROR: for web  Cannot start service web: oci runtime error: container_linux.go:247: starting container process caused "exec: \"/code/docker-entrypoint.sh\": stat /code/docker-entrypoint.sh: no such file or directory"
ERROR: Encountered errors while bringing up the project.

moss@DESKTOP-9LE20OE MINGW64 /c/develop/python/team-budget/budget_proj (dockerize)

Further testing by myself with other Docker containers on Windows 10 + Docker Toolbox for Windows resulted in similar errors (due to the same problem - can't find the script inside the container).

These same Docker containers will build and run successfully on Linux, MacOS and MacOS + Docker Toolbox for Mac configurations.

[MikeTheCanuck]

All other investigation by other members of the DevOps squad have hit similar dead-ends. There is no known explanation for why the same Docker containers will build and run correctly on Linux, MacOS and MacOS + Docker Toolbox for Mac.

The recommended workaround for Windows developers at this time is to use the following Vagrant box to enable Windows users to use Docker and perform other development tasks in a working *NIX environment: https://github.com/hackoregon/vagrant-for-docker

At this time there are no further plans by the DevOps squad to investigate, until additional information (e.g. detailed logs, other symptoms, links to possible fixes) become available. We have exhausted our own research approaches on this problem, and there is an available workaround.