Google Cloud CLI Docker
These are Docker images for the Google Cloud CLI.
The :latest
tag is Debian-based and includes default command
line tools of Google Cloud CLI (gcloud
, gsutil
, bq
) as well several
additional components.
Repositories
The Google Cloud CLI Docker Image is hosted on Container Registry.
The full repository name for Container Registry is gcr.io/google.com/cloudsdktool/google-cloud-cli
.
Supported tags
:latest
,:VERSION
: (large image with additional components pre-installed, Debian-based):slim
,:VERSION-slim
: (smaller image with no components pre-installed, Debian-based):alpine
,:VERSION-alpine
: (smallest image with no additional components installed, Alpine-based):debian_component_based
,:VERSION-debian_component_based
: (Similar to :latest but component installer based):emulators
,:VERSION
: (as small as possible with all the emulators)
→ Check out Container Registry for available tags.
Usage
To use this image, pull from Container Registry and then run the following command:
docker pull gcr.io/google.com/cloudsdktool/google-cloud-cli:latest
Verify the install
docker run gcr.io/google.com/cloudsdktool/google-cloud-cli:latest gcloud version
Google Cloud CLI 368.0.0
or use a particular version number:
docker run gcr.io/google.com/cloudsdktool/google-cloud-cli:368.0.0 gcloud version
You can authenticate gcloud
with your user credentials by running gcloud auth login
:
docker run -ti --name gcloud-config gcr.io/google.com/cloudsdktool/google-cloud-cli gcloud auth login
If you need to authenticate any program that uses the Google Cloud APIs, you need to pass the --update-adc
option:
docker run -ti --name gcloud-config gcr.io/google.com/cloudsdktool/google-cloud-cli gcloud auth login --update-adc
If you want to use a specific project for future uses, you can set this inside the gcloud-config
container:
docker run -ti --name gcloud-config gcr.io/google.com/cloudsdktool/google-cloud-cli /bin/bash -c 'gcloud auth login && gcloud config set project your-project'
Once you authenticate successfully, credentials are preserved in the volume of
the gcloud-config
container.
To list compute instances using these credentials, run the container with
--volumes-from
:
docker run --rm --volumes-from gcloud-config gcr.io/google.com/cloudsdktool/google-cloud-cli gcloud compute instances list --project your_project
NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS
instance-1 us-central1-a n1-standard-1 10.240.0.2 8.34.219.29 RUNNING
⚠️ Warning: Thegcloud-config
container now has a volume containing your Google Cloud credentials. Do not usegcloud-config
volume in other containers.
Alternatively, you can use auth/credential_file_override
property to set a path to a mounted service account
and then the config to read that using CLOUDSDK_CONFIG
environment variable.
for example, mycloud
configuration below has the auth/credential_file_override
already set and points towards a certificate file
that will be present within the container as a separate volume mount.
See issue#152
$ docker run -ti -e CLOUDSDK_CONFIG=/config/mygcloud \
-v `pwd`/mygcloud:/config/mygcloud \
-v `pwd`:/certs gcr.io/google.com/cloudsdktool/google-cloud-cli:alpine /bin/bash
bash-4.4# gcloud config list
[auth]
credential_file_override = /certs/svc_account.json
bash-4.4# head -10 /certs/svc_account.json
{
"type": "service_account",
"project_id": "project_id1",
....
bash-4.4# gcloud projects list
PROJECT_ID NAME PROJECT_NUMBER
project_id1 GCPAppID 1071284184432
You can set any Cloud SDK property via an ENV, please read and here.
Components Installed in Each Tag
Component | :latest | :alpine | :slim | :debian_component_based | :emulators |
---|---|---|---|---|---|
App Engine Go Extensions | x | x | |||
Appctl | |||||
BigQuery Command Line Tool | x | x | x | x | |
Cloud Bigtable Command Line Tool | x | x | |||
Cloud Bigtable Emulator | x | x | x | ||
Cloud Datalab Command Line Tool | x | x | |||
Cloud Datastore Emulator | x | x | x | ||
Cloud Firestore Emulator | x | x | |||
Cloud Pub/Sub Emulator | x | x | x | ||
Cloud SDK Core Libraries | x | x | x | x | |
Cloud SQL Proxy | |||||
Cloud Spanner Emulator | x | x | |||
Cloud Storage Command Line Tool | x | x | x | x | |
Google Cloud Build Local Builder | |||||
Google Container Registry's Docker credential helper | |||||
Kustomize | |||||
Minikube | |||||
Nomos CLI | |||||
Skaffold | |||||
anthos-auth | |||||
gcloud Alpha Commands | x | x | x | ||
gcloud Beta Commands | x | x | x | x | |
gcloud app Java Extensions | x | x | |||
gcloud app Python Extensions | x | x | |||
gcloud app Python Extensions (Extra Libraries) | x | x | |||
kpt | x | x | |||
kubectl | x | x | |||
local-extract | x | x |
Installing additional components
Debian-based images
cd debian_slim/
docker build --build-arg CLOUD_SDK_VERSION=159.0.0 \
--build-arg INSTALL_COMPONENTS="google-cloud-sdk-datastore-emulator" \
-t my-cloud-sdk-docker:slim .
Alpine-based images
To install additional components for Alpine-based images, create a Dockerfile
that uses the cloud-sdk
image as the base image. For example, to add kubectl
and
app-engine-java
components:
FROM gcr.io/google.com/cloudsdktool/google-cloud-cli:alpine
RUN apk --update add openjdk7-jre
RUN gcloud components install app-engine-java kubectl
and run:
docker build -t my-cloud-sdk-docker:alpine .
Note that in this case, you have to install dependencies of additional components manually.
Installing different version of gcloud sdk:
docker build -t my-cloud-sdk-docker:alpine --build-arg CLOUD_SDK_VERSION=<release_number> .
Legacy image (Google App Engine based)
The original image in this repository was based off of
FROM gcr.io/google_appengine/base
The full Dockerfile for that can be found
here for archival as well as in image tag
google/cloud-sdk-docker:legacy
Cloud SDK Release Tracking
You can also follow the Cloud SDK Release schedule here
Pinning version
Images tagged :latest
, :alpine
, :slim
and :debian_component_based
use
the most recent version of Google Cloud SDK, which may change its behaviour in
the future. List of components installed by default in each image can also
change between versions. To avoid such change breaking the tool you are using,
it is not recommended to use these tags in any production tools directly.
Instead use a particular version as listed in Supported tags
and update it periodically.