Absolute paths won't work on other machines

[dfalster]

After building a docker image, the launch script produced includes an absolute path, e.g. from mortality_bci

#!/bin/bash
set -e
$(boot2docker shellinit 2> /dev/null)
docker run -v /Users/rich/Documents/Projects/veg/mortality_bci:/src -it richfitz/mortality_bci $*

This won't run on collaborators machine because of absolute path. On the other hand docker requires absolute paths. Could we replace with something like generate the path with something like

#!/bin/bash
PWD=($pwd)
set -e
$(boot2docker shellinit 2> /dev/null)
docker run -v ($PWD)/..:/src -it richfitz/mortality_bci $*

[richfitz]

yeah, that seems like a far better option.

[dfalster]

except my proposed code doesn't quite work

[richfitz]

The issue of what we point the container at needs dealing with carefully. When I use these containers for projects I'm not actually using the launch script at all (sorry - just remembered). Look at the compose file in successional diversity:

  volumes:
    - ${PWD}/self:/root/successional_diversity

or

docker run --link docker_redis_1:redis -v ${PWD}/self:/root/successional_diversity -it richfitz/successional_diversity:latest R

see how self is being used here.

[dfalster]

Cool, that makes sense. For time being I manually edited the launch script to implement above, e.g. here

[richfitz]

Yeah, that looks way more sensible than what I had.