From adfc2cbcbc68003dd3f291251d2986703fb6878e Mon Sep 17 00:00:00 2001 From: Micah Zoltu Date: Sat, 19 Nov 2016 13:22:01 -0800 Subject: [PATCH] Minor technical correction. `$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`. --- docker-cloud/builds/advanced.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-cloud/builds/advanced.md b/docker-cloud/builds/advanced.md index 7649e6a04c..003a7d1466 100644 --- a/docker-cloud/builds/advanced.md +++ b/docker-cloud/builds/advanced.md @@ -20,7 +20,7 @@ processes and do not affect your service's run environment. * `COMMIT_MSG`: the message from the commit being tested and built. * `DOCKER_REPO`: the name of the Docker repository being built. * `DOCKER_TAG`: the Docker repository tag being built. -* `IMAGE_NAME`: the name and tag of the Docker repository being built. (This variable is a combination of `DOCKER_REPO`/`DOCKER_TAG`.) +* `IMAGE_NAME`: the name and tag of the Docker repository being built. (This variable is a combination of `DOCKER_REPO`:`DOCKER_TAG`.) If you are using these build environment variables in a `docker-compose.test.yml` file for automated testing, declare them in your `sut`