Provide Dockerfile

[kuanb]

Note, relates to Issue: #12

Dockerfile provides a clean, consistent environment for development and execution of library.

Making it available if desired. :)

[kuanb]

Not to rope @jalessio into this 😃 , but v helpful critique of this Dockerfile. Will revisit and make edits (again, just should anyone find this of use):

1. "too many layers… consolidate all those multiline commands into a single RUN like you have for the GEO libraries. Also, running apt-get update and apt-get install in separate RUN commands is a bit of an anti-pattern for a Dockerfile"

2. "also, I think you’re doing the “cleanup” step too early in the process — you should so that at the end, since the apt commands you run for GEOS will just re-populate /var/lib/apt"

[waddell]

Thank you for contributing this and for incorporating the original review feedback, Kuan. UDST has resumed active maintenance and reviewed the historical PR.

This targets the obsolete master branch and describes a 2017 development environment, so the Dockerfile should not be adopted as current build or release infrastructure. If UrbanAccess still needs a container after its supported Python versions, dependencies, and CI are established, we will create a new minimal image from the maintained packaging configuration.

Tracked in #95. We are leaving this open during the initial triage and will resolve it with the broader branch and infrastructure cleanup.