whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Separate docker's args

Browse Source
This commit is contained in:
Denis Kolodin
2016-10-16 12:23:27 +03:00
committed by GitHub
parent fc10dd34b2
commit 945878d072
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/hellonode.md
+2 -2
View File
@@ -145,7 +145,7 @@ docker stop hello_tutorial
Now that the image works as intended and is all tagged with your `$PROJECT_ID`, we can push it to the [Google Container Registry](https://cloud.google.com/tools/container-registry/), a private repository for your Docker images accessible from every Google Cloud project (but also from outside Google Cloud Platform) : Now that the image works as intended and is all tagged with your `$PROJECT_ID`, we can push it to the [Google Container Registry](https://cloud.google.com/tools/container-registry/), a private repository for your Docker images accessible from every Google Cloud project (but also from outside Google Cloud Platform) :
```shell ```shell
gcloud docker push gcr.io/$PROJECT_ID/hello-node:v1 gcloud docker -- push gcr.io/$PROJECT_ID/hello-node:v1
``` ```
If all goes well, you should be able to see the container image listed in the console: *Compute > Container Engine > Container Registry*. We now have a project-wide Docker image available which Kubernetes can access and orchestrate. If all goes well, you should be able to see the container image listed in the console: *Compute > Container Engine > Container Registry*. We now have a project-wide Docker image available which Kubernetes can access and orchestrate.
@@ -336,7 +336,7 @@ We can now build and publish a new container image to the registry with an incre
```shell ```shell
docker build -t gcr.io/$PROJECT_ID/hello-node:v2 . docker build -t gcr.io/$PROJECT_ID/hello-node:v2 .
gcloud docker push gcr.io/$PROJECT_ID/hello-node:v2 gcloud docker -- push gcr.io/$PROJECT_ID/hello-node:v2
``` ```
Building and pushing this updated image should be much quicker as we take full advantage of the Docker cache. Building and pushing this updated image should be much quicker as we take full advantage of the Docker cache.