Skip to content

Logging and Output

Debug

Enables debug mode with verbose logging.

            Argument: --debug, -d
Environment Variable: WATCHTOWER_DEBUG
                Type: Boolean
             Default: false

Note

Equivalent to --log-level debug. As an argument, it does not accept a value (e.g., --debug true is invalid).

See Maximum Log Level.

Trace

Enables trace mode with highly verbose logging, including sensitive information like credentials.

            Argument: --trace
Environment Variable: WATCHTOWER_TRACE
                Type: Boolean
             Default: false

Note

Equivalent to --log-level trace. As an argument, does not accept a value (e.g., --trace true is invalid).

See Maximum Log Level.

Warning

Use with caution due to credential exposure.

Maximum Log Level

Sets the maximum log level output to STDERR, visible in docker logs when running Watchtower in a container.

            Argument: --log-level
Environment Variable: WATCHTOWER_LOG_LEVEL
     Possible Values: panic, fatal, error, warn, info, debug, trace
             Default: info

Logging Format

Specifies the format for console log output.

            Argument: --log-format, -l
Environment Variable: WATCHTOWER_LOG_FORMAT
     Possible Values: Auto, LogFmt, Pretty, JSON
             Default: Auto

Disable ANSI Colors

Disables ANSI color escape codes in log output for plain text logs.

            Argument: --no-color
Environment Variable: NO_COLOR
                Type: Boolean
             Default: false

Programmatic Output (Porcelain)

Outputs session results in a machine-readable format.

            Argument: --porcelain, -P
Environment Variable: WATCHTOWER_PORCELAIN
     Possible Values: v1, json
             Default: None

Note

Equivalent to:

--notification-url logger://
--notification-log-stdout
--notification-report

Porcelain only fills in the notification-template, notification-report, and notification-log-stdout configuration options you have not set. A value you set yourself, with a flag or an environment variable, is kept.

For v1, the template is porcelain.v1.summary-no-log, producing one container per line.

For json, the template is porcelain.json, producing a JSON document:

{
  "containers": [
    {
      "name": "nginx",
      "image": "nginx:latest",
      "image_id": "abc123",
      "latest_image_id": "def456",
      "state": "Updated",
      "update_available": true
    }
  ]
}

Every container has these fields:

Field Meaning
name Container name
image Image name with tag
image_id Current short image ID
latest_image_id Latest short image ID
state Container state (Updated, Fresh, Failed, Skipped, Restarted, Stale)
update_available Whether the latest image differs from the current one

These fields are left out when they are empty:

Field Meaning
error Error message for the container
git_repo Git repository URL, as the .GitRepo template field
git_ref Git ref, as the .GitRef template field
changelog Changelog or releases URL, as the .Changelog template field
oci_source OCI image source, as the .Source template field
image_url OCI image URL, as the .ImageURL template field
documentation OCI documentation URL, as the .Documentation template field
current_image_version Version of the running image, as the .CurrentImageVersion template field
latest_image_version Version of a newer image, as the .LatestImageVersion template field
current_revision Revision of the running image, as the .CurrentImageRevision template field
latest_revision Revision of a newer image, as the .LatestImageRevision template field

See Git and OCI report fields for where each Git and OCI value comes from.