From 3164a2a9ea15ac3c74fb3960d904ea71b2b98d10 Mon Sep 17 00:00:00 2001 From: Victoria Bialas Date: Mon, 24 Jul 2017 14:56:18 -0400 Subject: [PATCH] fixed build command per user feedback (#3930) Signed-off-by: Victoria Bialas --- docker-cloud/builds/advanced.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docker-cloud/builds/advanced.md b/docker-cloud/builds/advanced.md index 1e71a9e647..45180a0261 100644 --- a/docker-cloud/builds/advanced.md +++ b/docker-cloud/builds/advanced.md @@ -80,7 +80,7 @@ Docker Cloud allows you to define build environment variables either in the hook In the following example, we define a build hook that uses `docker build` arguments to set the variable `CUSTOM` based on the value of variable we defined using the Docker Cloud build settings. `$IMAGE_NAME` is a variable that we provide with the name of the image being built. ```none -docker build --build-arg CUSTOM=$VAR -t $IMAGE_NAME +docker build --build-arg CUSTOM=$VAR -t $IMAGE_NAME . ``` > **Caution**: A `hooks/build` file overrides the basic [docker build](/engine/reference/commandline/build.md) command @@ -117,10 +117,10 @@ docker push $DOCKER_REPO:$SOURCE_COMMIT When Docker Cloud pulls a branch from a source code repository, it performs a shallow clone (only the tip of the specified branch). This has the advantage -of minimizing the amount of data transfer necessary from the repository and -speeding up the build because it pulls only the minimal code necessary. +of minimizing the amount of data transfer necessary from the repository and +speeding up the build because it pulls only the minimal code necessary. -Because of this, if you need to perform a custom action that relies on a different +Because of this, if you need to perform a custom action that relies on a different branch (such as a `post_push` hook), you won't be able checkout that branch, unless you do one of the following: