Merge branch 'master' into patch-1
This commit is contained in:
+5
-1
@@ -129,7 +129,7 @@ Let’s now stop the container. You can list the docker containers with:
|
||||
docker ps
|
||||
```
|
||||
|
||||
You should something like see:
|
||||
You should see something like this:
|
||||
|
||||
```shell
|
||||
CONTAINER ID IMAGE COMMAND NAMES
|
||||
@@ -150,8 +150,12 @@ 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 you see an error message like the following: __denied: Unable to create the repository, please check that you have access to do so.__ ensure that you are pushing the image to Container Registry with the correct user credentials, use `gcloud auth list` and then `gcloud config set account example@gmail.com`.
|
||||
|
||||

|
||||
|
||||
**Note:** *Docker for Windows, Version 1.12 or 1.12.1, does not yet support this procedure. Instead, it replies with the message 'denied: Unable to access the repository; please check that you have permission to access it'. A bugfix is available at http://stackoverflow.com/questions/39277986/unable-to-push-to-google-container-registry-unable-to-access-the-repository?answertab=votes#tab-top.*
|
||||
|
||||
## Create your Kubernetes Cluster
|
||||
|
||||
A cluster consists of a Master API server and a set of worker VMs called Nodes.
|
||||
|
||||
Reference in New Issue
Block a user