docs/docker-cloud/builds
Rob Jackson 6e0df9e39e Ensure custom build hooks consume DOCKERFILE_PATH (#6026)
I have a custom build hook to pass in build arguments on a repository from which I build two Docker images (tags), from two Dockerfiles.

My second build, however, with the custom Dockerfile, was not being built correctly. It was being built with the default `Dockerfile`, instead of my specified custom one.

I quickly figured out the custom build hook was to blame because it doesn't specify which Dockerfile it should build from, but there was no mention in the documentation of an environmental variable I can consume to get the custom "Dockerfile location" value. By dumping the env vars during the build process, I can there is an environmental variable with that value: `DOCKERFILE_PATH`.

This PR updates the documentation accordingly, to:

1) Expose the fact this environmental variable exists, and explains its purpose
2) Make sure its consumed in the example custom build hook, so any copy-pasters find themselves already supporting custom Dockerfiles, rather than struggling with the same problem
2018-02-23 16:35:55 -08:00
..
images Add Docker Cloud videos and updated redeploy note (#2765) 2017-04-13 13:10:44 -07:00
advanced.md Ensure custom build hooks consume DOCKERFILE_PATH (#6026) 2018-02-23 16:35:55 -08:00
automated-build.md Move /engine/installation to /install (#5651) 2018-01-26 10:29:14 -08:00
automated-testing.md Move /engine/installation to /install (#5651) 2018-01-26 10:29:14 -08:00
image-scan.md Add note on end of scanning preview service (#6007) 2018-02-14 08:56:47 -08:00
index.md WIP: re-organize docker cloud topics, public intro to swarm mode 2017-03-02 07:18:57 -08:00
link-source.md Various copyedits to reduce future tense, wordiness, and use of 'please' (#5788) 2018-01-25 17:37:23 -08:00
push-images.md Move /engine/installation to /install (#5651) 2018-01-26 10:29:14 -08:00
repos.md Various copyedits to reduce future tense, wordiness, and use of 'please' (#5788) 2018-01-25 17:37:23 -08:00