Unfortunately, (for practical and security reasons I guess), if you want to add/copy local content, it must be located under the same root path than the Dockerfile.
The <src> path must be inside the context of the build; you cannot ADD ../something/something, because the first step of a docker build is to send the context directory (and subdirectories) to the docker daemon.
EDIT: There's now an option (-f) to set the path of your Dockerfile ; it can be used to achieve what you want, see @Boedy 's response nelow.
Is there a "clean" workaround for this? I'd rather not restructure my whole project directory just to accommodate this. – ben_franklyNov 21 '14 at 18:35
Thank you! This works fine on a local box, but Docker Hub fails to build the image since it tries to do it from its same directory (tbh, just what one would normally expect). Is there any way to do the same trick in Docker Hub? – Marcel HernandezMar 25 at 20:31
Not that I know of. You could push the image to the registry instead of using automated build. – BoedyMar 29 at 9:15