To use the gcplogs driver as the default logging driver, set the log-driver and log-opt keys to appropriate values in the daemon.json file, which is located in /etc/docker/ on Linux hosts or C:\ProgramData\docker\config\daemon.json on Windows Server. For more about configuring Docker using daemon.json, see daemon.json.
The following example sets the log driver to gcplogs and sets the gcp-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:
docker run --log-driver=gcplogs …
This log driver does not implement a reader so it is incompatible with docker logs.
If Docker detects that it is running in a Google Cloud Project, it discovers configuration from the instance 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 the Google 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 Google Cloud 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 is not available. They do not override the values from metadata server.