From 5d9428c2a1291c6a1e5e96bb06e8d2540157cef7 Mon Sep 17 00:00:00 2001 From: Sandy Koh Date: Wed, 8 Apr 2020 11:08:52 +0100 Subject: [PATCH 1/7] docs: restructure build doc --- content/docs/using-appsody/building.md | 31 +++++++++++++++++++---- content/docs/using-appsody/deploying.md | 33 +++++++++---------------- 2 files changed, 37 insertions(+), 27 deletions(-) diff --git a/content/docs/using-appsody/building.md b/content/docs/using-appsody/building.md index d701bba72..f0a4689b8 100644 --- a/content/docs/using-appsody/building.md +++ b/content/docs/using-appsody/building.md @@ -13,10 +13,7 @@ If you want to build *and* deploy a Docker image directly to a locally installed The [appsody build](/docs/cli-commands/#appsody-build) command completes the following actions: - Extracts your code and other artifacts, including a new Dockerfile, which are required to build the *deployment* image from the *development* image. These files are saved to the `~/.appsody/extract` directory. -- Runs a `docker build` against the Dockerfile that was extracted on the previous step to produce a *deployment* image in your local Docker registry. - - If you want to give the image a name, specify the `-t ` parameter. - - If you want to push the built image to an image repository, specify the `--push` parameter. - - If you run `appsody build` with no parameters, the image is given a name that matches the name of your project. +- Runs a `docker build` against the Dockerfile that was extracted on the previous step to produce a *deployment* image in your local Docker registry. If you run `appsody build` with no parameters, the image is tagged with a name that matches the name of your project. - Generates a manifest called `app-deploy.yaml` that can be used to deploy your Appsody application. > If your project includes uppercase characters, these are converted to lowercase characters in the image name because Docker does not accept uppercase characters in image tags. Also, if your project directory includes underscore characters, those will be converted to dashes (-), because certain areas of Kubernetes are not tolerant of underscore characters. @@ -34,4 +31,28 @@ Project extracted to /Users/mchilant/.appsody/extract/appsody-project Running command: docker[build -t appsody-project -f /Users/mchilant/.appsody/extract/appsody-project/Dockerfile /Users/mchilant/.appsody/extract/appsody-project] Built docker image appsody-project Created deployment manifest: /Users/mchilant/appsody-project/app-deploy.yaml -``` \ No newline at end of file +``` + +### Pushing your application to Docker Hub + +If you would like to share your images to the Docker Hub registry, use the following command to push your application: +``` +appsody build -t --push +``` +This command completes the following actions: + +- Calls `appsody build` and creates a deployment image. +- The `-t mynamespace/myrepository[:tag]` flag tags the image. +- The `--push` flag pushes the image to Docker Hub. +- Generates a deployment manifest file named `app-deploy.yaml` in the project directory, if one doesn’t exist already. If a deployment manifest file exists, this command updates the following entries within it: application image, labels, and annotations. + +> If you don't specify `--push`, the image is available only on your local Docker registry. This flag is also available to the [appsody deploy](/docs/using-appsody/deploying) command. + +### Pushing your application to a custom registry +If you would like to share your images to a custom registry, use the following command to push your application: +``` +appsody build -t --push-url +``` +This command works similarly to the one above, the difference being the `--push-url` flag pushes the image to ``. + +> This will also trigger a push if the --push flag is not specified. This flag is also available to the [appsody deploy](/docs/using-appsody/deploying) command. \ No newline at end of file diff --git a/content/docs/using-appsody/deploying.md b/content/docs/using-appsody/deploying.md index 02269dec9..20e52a521 100644 --- a/content/docs/using-appsody/deploying.md +++ b/content/docs/using-appsody/deploying.md @@ -58,34 +58,23 @@ This command completes the following actions: - If you specified the `--knative` flag, or if Knative is the only deployment option for your stack, the command tags the image with the special prefix `dev.local`, making it accessible to your Kubernetes cluster (assuming you followed [these directions](/docs/using-appsody/installing-knative-locally)) - The deployment manifest, `app-deploy.yaml`, is used to issue a `kubectl apply -f` command against the target Kubernetes cluster so that the application can be deployed by the Appsody Operator. -### Deploying your application through Docker Hub - -If your cluster is configured to pull images from Docker Hub, use the following command to deploy your application: +### Deploying with different push and pull registries +If you are specifying different push and pull registries, for example, you might want to push to an external registry and pull from an internal registry, use the following command: ``` -appsody deploy -t --push --namespace mynamespace [--knative] +appsody deploy -t --push-url --pull-url ``` -The command completes the following actions: -- Calls `appsody build` and creates a deployment image, as described in the previous section. -- The `-t mynamespace/myrepository[:tag]` flag tags the image. -- The `--push` flag tells the Appsody CLI to push the image to Docker Hub. -- Creates a deployment manifest file named `app-deploy.yaml` in the project directory, if one doesn’t exist already. If a deployment manifest file exists, this command updates the following entries within it: application image, labels, and annotations. In addition, the `createKnativeService` entry is set to true if you specified the `--knative` flag. -- The Yaml file is used to issue a `kubectl apply -f` command against the target Kubernetes cluster. The Yaml file is set to use the Appsody operator. -- The `--namespace mynamespace` option provisions the deployment under the specified Kubernetes namespace within your cluster. +This command completes the following actions: -> If you don't specify `--push`, the image is available only on your local Docker registry and the target Kubernetes cluster must be configured to have access to your local Docker registry. +- Calls `appsody build` and creates a deployment image. +- The `-t mynamespace/myrepository[:tag]` flag tags the image. +- The `--push-url` pushes the image to ``. +- Generates a deployment manifest file, "app-deploy.yaml", if one is not present, then applies it to your Kubernetes cluster. +- The `--pull-url` injects `` into the deployment manifest for Kubernetes to pull the correct image. +- Deploys your image to your Kubernetes cluster via the Appsody operator, or as a Knative service if you specify the "--knative" flag. -### Deploying your application to a custom registry -If your cluster is configured to pull images from a custom registry, use the following command to deploy your application: -``` -appsody deploy -t --push-url -``` +> If an Appsody operator cannot be found, one will be installed on your cluster. -If you are specifying different push and pull registries, for example, you might want to push to an external registry and pull from an internal registry, use the following command: -``` -appsody deploy -t --push-url --pull-url -``` -> Note: The pull registry url gets injected into the deployment manifest for Kubernetes to pull the correct image. ### Deploying multiple projects If you are running multiple Appsody projects on your workstation, you can use `appsody deploy` and `appsody operator` commands to get them deployed to a Kubernetes cluster. However, make sure that you run these commands one at a time, because those commands create temporary files that might lead to conflicts if created concurrently. From c633b5a6b1cfe17b9b09ffe9d57bb53920c33b1d Mon Sep 17 00:00:00 2001 From: Sandy Koh Date: Wed, 8 Apr 2020 11:16:52 +0100 Subject: [PATCH 2/7] add links to appsody operator --- content/docs/using-appsody/deploying.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/using-appsody/deploying.md b/content/docs/using-appsody/deploying.md index 20e52a521..bcf3d0a34 100644 --- a/content/docs/using-appsody/deploying.md +++ b/content/docs/using-appsody/deploying.md @@ -71,9 +71,9 @@ This command completes the following actions: - The `--push-url` pushes the image to ``. - Generates a deployment manifest file, "app-deploy.yaml", if one is not present, then applies it to your Kubernetes cluster. - The `--pull-url` injects `` into the deployment manifest for Kubernetes to pull the correct image. -- Deploys your image to your Kubernetes cluster via the Appsody operator, or as a Knative service if you specify the "--knative" flag. +- Deploys your image to your Kubernetes cluster via the [Appsody operator](/docs/reference/appsody-operator), or as a Knative service if you specify the "--knative" flag. -> If an Appsody operator cannot be found, one will be installed on your cluster. +> If an [Appsody operator](/docs/reference/appsody-operator) cannot be found, one will be installed on your cluster. ### Deploying multiple projects From 88448abee0639bb1daded6e64f36f323dcddfe04 Mon Sep 17 00:00:00 2001 From: Sandy Koh Date: Wed, 8 Apr 2020 12:38:06 +0100 Subject: [PATCH 3/7] requested changes --- content/docs/using-appsody/building.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/using-appsody/building.md b/content/docs/using-appsody/building.md index f0a4689b8..43bda3586 100644 --- a/content/docs/using-appsody/building.md +++ b/content/docs/using-appsody/building.md @@ -46,13 +46,13 @@ This command completes the following actions: - The `--push` flag pushes the image to Docker Hub. - Generates a deployment manifest file named `app-deploy.yaml` in the project directory, if one doesn’t exist already. If a deployment manifest file exists, this command updates the following entries within it: application image, labels, and annotations. -> If you don't specify `--push`, the image is available only on your local Docker registry. This flag is also available to the [appsody deploy](/docs/using-appsody/deploying) command. +> If you don't specify the `--push` flag, the image is available only on your local Docker registry. The `--push` flag is also available to the [appsody deploy](/docs/using-appsody/deploying) command. ### Pushing your application to a custom registry If you would like to share your images to a custom registry, use the following command to push your application: ``` appsody build -t --push-url ``` -This command works similarly to the one above, the difference being the `--push-url` flag pushes the image to ``. +The `--push-url` flag pushes the image to a registry URL at a port that you specify with ``. -> This will also trigger a push if the --push flag is not specified. This flag is also available to the [appsody deploy](/docs/using-appsody/deploying) command. \ No newline at end of file +> A push is triggered when using the `--push-url` flag even if the `--push` flag is not specified. The `--push` and `--push-url` flags are also available to the [appsody deploy](/docs/using-appsody/deploying) command. \ No newline at end of file From 1ccebf145374a92ecdcef5eb74f78f88caf34fc0 Mon Sep 17 00:00:00 2001 From: Sandy Koh Date: Tue, 14 Apr 2020 13:51:43 +0100 Subject: [PATCH 4/7] requested restructuring --- content/docs/using-appsody/building.md | 26 ++++++++++++++++++++----- content/docs/using-appsody/deploying.md | 7 +++++-- 2 files changed, 26 insertions(+), 7 deletions(-) diff --git a/content/docs/using-appsody/building.md b/content/docs/using-appsody/building.md index 43bda3586..73bf492ec 100644 --- a/content/docs/using-appsody/building.md +++ b/content/docs/using-appsody/building.md @@ -13,7 +13,7 @@ If you want to build *and* deploy a Docker image directly to a locally installed The [appsody build](/docs/cli-commands/#appsody-build) command completes the following actions: - Extracts your code and other artifacts, including a new Dockerfile, which are required to build the *deployment* image from the *development* image. These files are saved to the `~/.appsody/extract` directory. -- Runs a `docker build` against the Dockerfile that was extracted on the previous step to produce a *deployment* image in your local Docker registry. If you run `appsody build` with no parameters, the image is tagged with a name that matches the name of your project. +- Runs a `docker build` against the Dockerfile that was extracted on the previous step to produce a *deployment* image in your local Docker registry. - Generates a manifest called `app-deploy.yaml` that can be used to deploy your Appsody application. > If your project includes uppercase characters, these are converted to lowercase characters in the image name because Docker does not accept uppercase characters in image tags. Also, if your project directory includes underscore characters, those will be converted to dashes (-), because certain areas of Kubernetes are not tolerant of underscore characters. @@ -33,7 +33,23 @@ Built docker image appsody-project Created deployment manifest: /Users/mchilant/appsody-project/app-deploy.yaml ``` -### Pushing your application to Docker Hub +## Tagging your application image + +If you would like to tag your application image with a name, use the following command: +``` +appsody build -t +``` +This command completes the following actions: + +- Calls `appsody build` and creates a deployment image. +- The `-t` flag tags the image with the name `mynamespace/myrepository[:tag]`. + +> If you don't specify the `-t` flag, the image is tagged with a name that matches the name of your project. + + +## Pushing your application image to an image registry + +### Pushing to Docker Hub If you would like to share your images to the Docker Hub registry, use the following command to push your application: ``` @@ -42,14 +58,14 @@ appsody build -t --push This command completes the following actions: - Calls `appsody build` and creates a deployment image. -- The `-t mynamespace/myrepository[:tag]` flag tags the image. +- The `-t` flag tags the image with the name `mynamespace/myrepository[:tag]`. - The `--push` flag pushes the image to Docker Hub. - Generates a deployment manifest file named `app-deploy.yaml` in the project directory, if one doesn’t exist already. If a deployment manifest file exists, this command updates the following entries within it: application image, labels, and annotations. > If you don't specify the `--push` flag, the image is available only on your local Docker registry. The `--push` flag is also available to the [appsody deploy](/docs/using-appsody/deploying) command. -### Pushing your application to a custom registry -If you would like to share your images to a custom registry, use the following command to push your application: +## Pushing to a custom registry +By default, the `--push` flag shares your images to the Docker Hub registry. If you would like to share your images to a custom registry, use the following command to push your application: ``` appsody build -t --push-url ``` diff --git a/content/docs/using-appsody/deploying.md b/content/docs/using-appsody/deploying.md index bcf3d0a34..aaa3cdd68 100644 --- a/content/docs/using-appsody/deploying.md +++ b/content/docs/using-appsody/deploying.md @@ -58,8 +58,11 @@ This command completes the following actions: - If you specified the `--knative` flag, or if Knative is the only deployment option for your stack, the command tags the image with the special prefix `dev.local`, making it accessible to your Kubernetes cluster (assuming you followed [these directions](/docs/using-appsody/installing-knative-locally)) - The deployment manifest, `app-deploy.yaml`, is used to issue a `kubectl apply -f` command against the target Kubernetes cluster so that the application can be deployed by the Appsody Operator. -### Deploying with different push and pull registries -If you are specifying different push and pull registries, for example, you might want to push to an external registry and pull from an internal registry, use the following command: +### Deploying to a private registry + +If you are pulling your image from a registry within your cluster, the registry may only be accessed by using a different name from outside your cluster, and a different name from within your cluster. For example, you might want to push to an external registry and pull from an internal registry. + +To specify different push and pull registries, use the following command: ``` appsody deploy -t --push-url --pull-url ``` From 3a63b4d14d22789de2312a89a931bea2394128d6 Mon Sep 17 00:00:00 2001 From: Sandy Koh Date: Mon, 20 Apr 2020 14:03:17 +0100 Subject: [PATCH 5/7] requested restructuring --- content/docs/using-appsody/building.md | 32 ++++++++++++-------------- 1 file changed, 15 insertions(+), 17 deletions(-) diff --git a/content/docs/using-appsody/building.md b/content/docs/using-appsody/building.md index 73bf492ec..178936e29 100644 --- a/content/docs/using-appsody/building.md +++ b/content/docs/using-appsody/building.md @@ -14,7 +14,7 @@ The [appsody build](/docs/cli-commands/#appsody-build) command completes the fol - Extracts your code and other artifacts, including a new Dockerfile, which are required to build the *deployment* image from the *development* image. These files are saved to the `~/.appsody/extract` directory. - Runs a `docker build` against the Dockerfile that was extracted on the previous step to produce a *deployment* image in your local Docker registry. -- Generates a manifest called `app-deploy.yaml` that can be used to deploy your Appsody application. +- Generates a deployment manifest file named `app-deploy.yaml` in the project directory, if one doesn’t exist already. If a deployment manifest file exists, this command updates the following entries within it: application image, labels, and annotations. > If your project includes uppercase characters, these are converted to lowercase characters in the image name because Docker does not accept uppercase characters in image tags. Also, if your project directory includes underscore characters, those will be converted to dashes (-), because certain areas of Kubernetes are not tolerant of underscore characters. @@ -35,40 +35,38 @@ Created deployment manifest: /Users/mchilant/appsody-project/app-deploy.yaml ## Tagging your application image -If you would like to tag your application image with a name, use the following command: +To tag the built application image, use the `-t ` flag along with the `build` command. The tag can be specified in the format `mynamespace/myrepository[:tag]`. + +For example: ``` appsody build -t ``` -This command completes the following actions: - -- Calls `appsody build` and creates a deployment image. -- The `-t` flag tags the image with the name `mynamespace/myrepository[:tag]`. +The application image built by `appsody build` will be tagged with the name `mynamespace/myrepository[:tag]`. -> If you don't specify the `-t` flag, the image is tagged with a name that matches the name of your project. +> If the `-t` flag is not specified, the image is tagged with the project name. ## Pushing your application image to an image registry ### Pushing to Docker Hub -If you would like to share your images to the Docker Hub registry, use the following command to push your application: +To share your images to the Docker Hub registry, use the `--push` flag along with the `build` command. + +For example: ``` appsody build -t --push ``` -This command completes the following actions: - -- Calls `appsody build` and creates a deployment image. -- The `-t` flag tags the image with the name `mynamespace/myrepository[:tag]`. -- The `--push` flag pushes the image to Docker Hub. -- Generates a deployment manifest file named `app-deploy.yaml` in the project directory, if one doesn’t exist already. If a deployment manifest file exists, this command updates the following entries within it: application image, labels, and annotations. +The application image built by `appsody build` will be tagged with the name `mynamespace/myrepository[:tag]`, and pushed to the Docker Hub registry. > If you don't specify the `--push` flag, the image is available only on your local Docker registry. The `--push` flag is also available to the [appsody deploy](/docs/using-appsody/deploying) command. -## Pushing to a custom registry -By default, the `--push` flag shares your images to the Docker Hub registry. If you would like to share your images to a custom registry, use the following command to push your application: +### Pushing to a custom registry +By default, the `--push` flag shares your images to the Docker Hub registry. To share your images to a custom registry, use the `--push-url ` flag along with the `build` command. + +For example: ``` appsody build -t --push-url ``` -The `--push-url` flag pushes the image to a registry URL at a port that you specify with ``. +The application image built by `appsody build` will be tagged with the name `mynamespace/myrepository[:tag]`, and pushed to the registry at the URL that you specify with ``. > A push is triggered when using the `--push-url` flag even if the `--push` flag is not specified. The `--push` and `--push-url` flags are also available to the [appsody deploy](/docs/using-appsody/deploying) command. \ No newline at end of file From e55d01faab6ce822794894c59b50dcd7c2ef8d15 Mon Sep 17 00:00:00 2001 From: Sandy Koh Date: Mon, 20 Apr 2020 14:38:07 +0100 Subject: [PATCH 6/7] requested changes --- content/docs/using-appsody/building.md | 8 +++--- content/docs/using-appsody/deploying.md | 34 +++++++++++++++---------- 2 files changed, 25 insertions(+), 17 deletions(-) diff --git a/content/docs/using-appsody/building.md b/content/docs/using-appsody/building.md index 178936e29..8a06c664f 100644 --- a/content/docs/using-appsody/building.md +++ b/content/docs/using-appsody/building.md @@ -50,7 +50,7 @@ The application image built by `appsody build` will be tagged with the name `myn ### Pushing to Docker Hub -To share your images to the Docker Hub registry, use the `--push` flag along with the `build` command. +To push the built application image to the Docker Hub registry, use the `--push` flag along with the `build` command. For example: ``` @@ -58,10 +58,10 @@ appsody build -t --push ``` The application image built by `appsody build` will be tagged with the name `mynamespace/myrepository[:tag]`, and pushed to the Docker Hub registry. -> If you don't specify the `--push` flag, the image is available only on your local Docker registry. The `--push` flag is also available to the [appsody deploy](/docs/using-appsody/deploying) command. +> If the `--push` flag is not specified, the image is available only on your local Docker registry. ### Pushing to a custom registry -By default, the `--push` flag shares your images to the Docker Hub registry. To share your images to a custom registry, use the `--push-url ` flag along with the `build` command. +To push the built application image to a custom registry, use the `--push-url ` flag along with the `build` command. For example: ``` @@ -69,4 +69,4 @@ appsody build -t --push-url ``` The application image built by `appsody build` will be tagged with the name `mynamespace/myrepository[:tag]`, and pushed to the registry at the URL that you specify with ``. -> A push is triggered when using the `--push-url` flag even if the `--push` flag is not specified. The `--push` and `--push-url` flags are also available to the [appsody deploy](/docs/using-appsody/deploying) command. \ No newline at end of file +> If `--push-url` flag is not specified, the image is pushed to DockerHub. A push is triggered when using the `--push-url` flag even if the `--push` flag is not specified. \ No newline at end of file diff --git a/content/docs/using-appsody/deploying.md b/content/docs/using-appsody/deploying.md index aaa3cdd68..02269dec9 100644 --- a/content/docs/using-appsody/deploying.md +++ b/content/docs/using-appsody/deploying.md @@ -58,26 +58,34 @@ This command completes the following actions: - If you specified the `--knative` flag, or if Knative is the only deployment option for your stack, the command tags the image with the special prefix `dev.local`, making it accessible to your Kubernetes cluster (assuming you followed [these directions](/docs/using-appsody/installing-knative-locally)) - The deployment manifest, `app-deploy.yaml`, is used to issue a `kubectl apply -f` command against the target Kubernetes cluster so that the application can be deployed by the Appsody Operator. -### Deploying to a private registry +### Deploying your application through Docker Hub -If you are pulling your image from a registry within your cluster, the registry may only be accessed by using a different name from outside your cluster, and a different name from within your cluster. For example, you might want to push to an external registry and pull from an internal registry. - -To specify different push and pull registries, use the following command: +If your cluster is configured to pull images from Docker Hub, use the following command to deploy your application: ``` -appsody deploy -t --push-url --pull-url +appsody deploy -t --push --namespace mynamespace [--knative] ``` +The command completes the following actions: -This command completes the following actions: - -- Calls `appsody build` and creates a deployment image. +- Calls `appsody build` and creates a deployment image, as described in the previous section. - The `-t mynamespace/myrepository[:tag]` flag tags the image. -- The `--push-url` pushes the image to ``. -- Generates a deployment manifest file, "app-deploy.yaml", if one is not present, then applies it to your Kubernetes cluster. -- The `--pull-url` injects `` into the deployment manifest for Kubernetes to pull the correct image. -- Deploys your image to your Kubernetes cluster via the [Appsody operator](/docs/reference/appsody-operator), or as a Knative service if you specify the "--knative" flag. +- The `--push` flag tells the Appsody CLI to push the image to Docker Hub. +- Creates a deployment manifest file named `app-deploy.yaml` in the project directory, if one doesn’t exist already. If a deployment manifest file exists, this command updates the following entries within it: application image, labels, and annotations. In addition, the `createKnativeService` entry is set to true if you specified the `--knative` flag. +- The Yaml file is used to issue a `kubectl apply -f` command against the target Kubernetes cluster. The Yaml file is set to use the Appsody operator. +- The `--namespace mynamespace` option provisions the deployment under the specified Kubernetes namespace within your cluster. + +> If you don't specify `--push`, the image is available only on your local Docker registry and the target Kubernetes cluster must be configured to have access to your local Docker registry. -> If an [Appsody operator](/docs/reference/appsody-operator) cannot be found, one will be installed on your cluster. +### Deploying your application to a custom registry +If your cluster is configured to pull images from a custom registry, use the following command to deploy your application: +``` +appsody deploy -t --push-url +``` +If you are specifying different push and pull registries, for example, you might want to push to an external registry and pull from an internal registry, use the following command: +``` +appsody deploy -t --push-url --pull-url +``` +> Note: The pull registry url gets injected into the deployment manifest for Kubernetes to pull the correct image. ### Deploying multiple projects If you are running multiple Appsody projects on your workstation, you can use `appsody deploy` and `appsody operator` commands to get them deployed to a Kubernetes cluster. However, make sure that you run these commands one at a time, because those commands create temporary files that might lead to conflicts if created concurrently. From ebe01bd45757d05041f1591b8a8a05699fa773a3 Mon Sep 17 00:00:00 2001 From: Sandy Koh Date: Mon, 20 Apr 2020 15:24:04 +0100 Subject: [PATCH 7/7] separate notes --- content/docs/using-appsody/building.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/docs/using-appsody/building.md b/content/docs/using-appsody/building.md index 8a06c664f..7a5c51dd5 100644 --- a/content/docs/using-appsody/building.md +++ b/content/docs/using-appsody/building.md @@ -63,10 +63,12 @@ The application image built by `appsody build` will be tagged with the name `myn ### Pushing to a custom registry To push the built application image to a custom registry, use the `--push-url ` flag along with the `build` command. +> A push is triggered when using the `--push-url` flag even if the `--push` flag is not specified. + For example: ``` appsody build -t --push-url ``` The application image built by `appsody build` will be tagged with the name `mynamespace/myrepository[:tag]`, and pushed to the registry at the URL that you specify with ``. -> If `--push-url` flag is not specified, the image is pushed to DockerHub. A push is triggered when using the `--push-url` flag even if the `--push` flag is not specified. \ No newline at end of file +> If the `--push-url` flag is not specified, the image is pushed to DockerHub. \ No newline at end of file