updating readme and dockerfile

tools/cloud-build/images/cluster-toolkit-dockerfile/Dockerfile

@@ -77,4 +77,4 @@ RUN echo $PATH
 
 # Command to execute when running the container (placeholder)
 ENTRYPOINT ["gcluster"]
-CMD ["--version"]
+CMD ["--help"]

tools/cloud-build/images/cluster-toolkit-dockerfile/README.md

@@ -4,18 +4,18 @@ This repository contains a Dockerfile for building a Docker image with Cluster T
 
 ## System Requirements
 
-* [Docker Engine](https://docs.docker.com/engine/) needs to be installed.
+* [Docker Engine](https://docs.docker.com/engine/) needs to be installed to build a Docker image from this Dockerfile.
 
-## Environment Variables
-The following environment variables can be used to customize the build process:
+## Build Arguments
+The following build arguments can be used to customize the build process:
 * **`BASE_IMAGE`**: The base image to use for the build. Defaults to `gcr.io/google.com/cloudsdktool/google-cloud-cli:stable`.
 * **`TERRAFORM_VERSION`**: The version of Terraform to install. Defaults to `1.5.2`.
 * **`PACKER_VERSION`**: The version of Packer to install. Defaults to `1.8.6`.
 * **`GO_VERSION`**: The version of Go to install. Defaults to `1.21.0`.
 * **`CLUSTER_TOOLKIT_VERSION`**: The version (tag) of the Cluster Toolkit to install. Defaults to the current version associated with the `main` branch of the cluster toolkit repository.
 
-## Build the Docker Image
-To build the Docker image, navigate to the directory the Dockerfile is present in and run the following command:
+## Build the Cluster Toolkit Docker Image
+To build the Cluster Toolkit Docker image, navigate to the directory the Dockerfile is present in and run the following command:
 
 ```bash
 docker build --build-arg BASE_IMAGE=<base_image> \
@@ -34,51 +34,26 @@ docker build --build-arg CLUSTER_TOOLKIT_VERSION=v1.40.0 -t my-cluster-toolkit-i
 
 The above example builds an image tagged `my-cluster-toolkit-image` and sets the CLUSTER_TOOLKIT_VERSION to v1.40.0 while using the default values for other arguments.
 
-## Run the Docker Image
-To run the Docker image, use the following command:
+## Run the Cluster Toolkit Docker Image
+To run the Cluster Toolkit Docker image, use the following command:
 
 ```bash
-docker run <image_name> <gcluster_command>
+docker run -v ~/.config/gcloud/:/root/.config/gcloud -v $(pwd):/data <image_name> <gcluster_command>
 ```
 
-Replace the following placeholders:
+This command runs the Cluster Toolkit Docker image and allows the `gcluster` binary to access your Google Cloud credentials and local files. Here's a breakdown:
 
-* `<image_name>`: The name of your Docker image.
-* `<gcluster_command>`: The gcluster command you want to execute.
+* `-v ~/.config/gcloud/:/root/.config/gcloud`: This part mounts your local Google Cloud configuration directory `(~/.config/gcloud)` to the `/root/.config/gcloud` directory inside the container. This allows the `gcluster` binary to access your credentials and interact with Google Cloud resources.
+* `-v $(pwd):/data`: This part mounts your current working directory `($(pwd))` to the `/data` directory inside the container. This allows you to access any files in your current directory (like blueprint files) from within the container. You can then reference these files in your `<gcluster_command>` using the `/data` path.
+* `<image_name>`: Replace this with the name of your Docker image.
+* `<gcluster_command>`: Replace this with the `gcluster` command you want to execute. The Cluster Toolkit Docker image has `ENTRYPOINT ["gcluster"]` in its Dockerfile. This means that the `gcluster` command is automatically executed when the container starts, and any arguments provided after `<image_name>` in the docker run command are passed as arguments to `gcluster`.
 
-Because this Dockerfile has an `ENTRYPOINT ["gcluster"]` line, any arguments provided to the docker run command after the `<image_name>` will be passed as arguments to the `gcluster` command within the container.
+When using the docker container to run `gcluster` commands that either deploy or modify cloud resources, it's strongly recommended to save a local copy of the deployment folder that's generated inside of the docker container. This can be done by using the `--out` flag in combination with some `gcluster` commands to set the output directory where the `gcluster` deployment directory will be created. Ideally, the output directory should be a directory mounted from your local machine to the docker container. This ensures that the deployment folder persists even after the container exits, allowing you to access and manage the deployment artifacts even after the container is removed.
 
 Example:
 
-```bash
-docker run my-cluster-toolkit-image --version
-```
-
-This command will execute `gcluster --version` within the container. You can use this pattern to run any valid gcluster command within the container.
-
-## Sharing data between local and container environments
-To use gcluster commands that interact with Google Cloud, you need to provide your Google Cloud credentials to the container. You can do this by mounting your gcloud configuration directory:
-
-```bash
-docker run -v ~/.config/gcloud/:/root/.config/gcloud <image_name> <gcluster_command>
-```
-
-This mounts your local `~/.config/gcloud` directory to the `/root/.config/gcloud` directory inside the container, allowing the gcluster binary to access your credentials.
-
-To pass in a blueprint stored locally to the `glcuster` binary inside of the container, you can also mount the directory containing the blueprint to the container:
-
-```bash
-docker run -v ~/.config/gcloud/:/root/.config/gcloud -v $(pwd):/data <image_name> <gcluster_command>
-```
-
-This mounts your current working directory ($(pwd)) to the `/data` directory inside the container. You can then reference the blueprint file within your <gcluster_command> using the /data path.
-
-When using the docker container to run gcluster commands that either deploy or modify cloud resources, it's strongly recommended to save a local copy of the deployment folder that's generated inside of the docker container. This can be done by using the `--out` flag in combination with some `gcluster` sub-commands to set the output directory where the gcluster deployment directory will be created. Ideally, the output directory should be a directory mounted from your local machine to the docker container. This ensures that the deployment folder persists even after the container exits.
-
-Here's an example of how to use the `--out` flag to save the deployment folder to your current directory (mounted as `/data` in the container) when the `deploy` sub-command is used:
-
 ```bash
 docker run -v ~/.config/gcloud/:/root/.config/gcloud -v $(pwd):/data my-cluster-toolkit-image deploy /data/my-blueprint.yaml --out /data --auto-approve
 ```
 
-In this example, the deployment folder will be created in your current directory on your local machine, allowing you to access and manage the deployment artifacts even after the container is removed. The `--auto-approve` flag automatically approves any prompts from gcluster, streamlining the deployment process.
+This example runs the `deploy` command with the blueprint file `my-blueprint.yaml` located in your current directory. The `--out /data` flag saves the deployment folder to your current directory, and `--auto-approve` automatically approves any prompts from `gcluster`, streamlining the deployment process.