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
* Reword lots of instances of 'will'
* Reword lots of instances of won't
* Reword lots of instances of we'll
* Eradicate you'll
* Eradicate 'be able to' type of phrases
* Eradicate 'unable to' type of phrases
* Eradicate 'has / have to' type of phrases
* Eradicate 'note that' type of phrases
* Eradicate 'in order to' type of phrases
* Redirect to official Chef and Puppet docs
* Eradicate gratuitous 'please'
* Reduce use of e.g.
* Reduce use of i.e.
* Reduce use of N.B.
* Get rid of 'sexagesimal' and correct some errors
It seems unclear from documentation what format and other options the docker-compose.test.yml may have. By specifying that its structure is similar to docker-cloud.yml developers will get a hint of where to search for further docker-compose.test.yml specification.
* added Anaconda Python 3.5.2 install/run to known issues
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added notes re: Python 3.x not supported in setup and install
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* fixed heading levels in Cloud known errors
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* fixed links (moby --> docker), formatting
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* fixed on-page link list alignments for toc max/min topics
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* Updates to automated tests doc
Updated automated test doc to reflect new autotest behavior.
* made minor formatting changes
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* tweak: code format for filename
slight reword, so as to avoid confusion w/filename
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* small changes just to kick build again
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added videos links re:auto build, testing, and redeploy
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added images for video cues, and redeploy note
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
Remove reference to DSS only be enabled on Docker Cloud individual accounts:
> **Note**: Docker Hub can display Security Scan results for organizations and teams, however Security Scanning can only be enabled on Docker Cloud individual accounts at this time.
edited screen snap
breaking out topics for Docker Cloud swarm mode
added another where-to-next link
added more where-to-next links
added back in on-page TOC for create swarm topic
incorporated Ryan's review comments on first draft
more Ryan's review comments, sweep thru all for consistency, notoc on short pages, etc.
removed duplicate link to 'create a new swarm in docker cloud'
Laura's comments incorporated
re-organized Cloud topics, added in Swarm Mode
Ryan's review comments on Cloud, added new type of advisory for Beta previews
more review comments, manage infrastructure --> standard mode
fixing image
testing cloud images
updates to Cloud welcome page for Swarm, non-Swarm descriptions
add new cloud repository image
retake of corrupted image
fixed the other instance of corrupted image by referencing the retake
fixing corrupted image on GitHub
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
edited screen snap
breaking out topics for Docker Cloud swarm mode
added another where-to-next link
added more where-to-next links
added back in on-page TOC for create swarm topic
incorporated Ryan's review comments on first draft
more Ryan's review comments, sweep thru all for consistency, notoc on short pages, etc.
removed duplicate link to 'create a new swarm in docker cloud'
Laura's comments incorporated
re-organized Cloud topics, added in Swarm Mode
Ryan's review comments on Cloud, added new type of advisory for Beta previews
more review comments, manage infrastructure --> standard mode
fixing image
testing cloud images
updates to Cloud welcome page for Swarm, non-Swarm descriptions
add new cloud repository image
retake of corrupted image
fixed the other instance of corrupted image by referencing the retake
fixing corrupted image on GitHub
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
`$IMAGE_NAME` is actually `$DOCKER_REPO:$DOCKER_TAG`, not `$DOCKER_REPO/$DOCKER_TAG`. This mistake confused me and made me think that `$DOCKER_REPO` was something like `index.docker.io/MyName` rather than `index.docker.io/MyName/MyProject`.
Gwendolynne Barr
Rob Jackson
Bryan Lee
Misty Stanley-Jones
Alex Villarreal
Oleksii Trekhleb
Bhavin Gandhi
Victoria Bialas
Peter Kokot
Ryan Kennedy
Wilfred van der Deijl
Victoria Bialas
Constanze Kratel
Shubheksha Jalan
Cory Locklear
Wang Jie
LRubin
Adrien Duermael
Peter Dave Hello
luojie233
Adrien Duermael
Micah Zoltu