Google Cloud Logging driver (original) (raw)
The Google Cloud Logging driver sends container logs toGoogle Cloud LoggingLogging.
To use the gcplogs driver as the default logging driver, set the log-driverand log-opt keys to appropriate values in the daemon.json file, which is located in /etc/docker/ on Linux hosts orC:\ProgramData\docker\config\daemon.json on Windows Server. For more about configuring Docker using daemon.json, seedaemon.json.
The following example sets the log driver to gcplogs and sets thegcp-meta-name option.
Restart Docker for the changes to take effect.
You can set the logging driver for a specific container by using the--log-driver option to docker run:
If Docker detects that it's running in a Google Cloud Project, it discovers configuration from theinstance metadata service. Otherwise, the user must specify which project to log to using the --gcp-project log option and Docker attempts to obtain credentials from theGoogle Application Default Credential. The --gcp-project flag takes precedence over information discovered from the metadata server, so a Docker daemon running in a Google Cloud project can be overridden to log to a different project using --gcp-project.
Docker fetches the values for zone, instance name and instance ID from Google Cloud metadata server. Those values can be provided via options if metadata server isn't available. They don't override the values from metadata server.
You can use the --log-opt NAME=VALUE flag to specify these additional Google Cloud Logging driver options:
| Option | Required | Description |
|---|---|---|
| gcp-project | optional | Which Google Cloud project to log to. Defaults to discovering this value from the Google Cloud metadata server. |
| gcp-log-cmd | optional | Whether to log the command that the container was started with. Defaults to false. |
| labels | optional | Comma-separated list of keys of labels, which should be included in message, if these labels are specified for the container. |
| labels-regex | optional | Similar to and compatible with labels. A regular expression to match logging-related labels. Used for advancedlog tag options. |
| env | optional | Comma-separated list of keys of environment variables, which should be included in message, if these variables are specified for the container. |
| env-regex | optional | Similar to and compatible with env. A regular expression to match logging-related environment variables. Used for advancedlog tag options. |
| gcp-meta-zone | optional | Zone name for the instance. |
| gcp-meta-name | optional | Instance name. |
| gcp-meta-id | optional | Instance ID. |
If there is collision between label and env keys, the value of the envtakes precedence. Both options add additional fields to the attributes of a logging message.
The following is an example of the logging options required to log to the default logging destination which is discovered by querying the Google Cloud metadata server.
This configuration also directs the driver to include in the payload the labellocation, the environment variable ENV, and the command used to start the container.
The following example shows logging options for running outside of Google Cloud. The GOOGLE_APPLICATION_CREDENTIALS environment variable must be set for the daemon, for example via systemd: