mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-06-23 05:58:04 +00:00
README: logging: add shimv2 information
The shimv2 runtime logs slightly differently - let's clarify that in the existing OCI/CRI-O only runtime section. Fixes: #2520 Signed-off-by: Graham Whaley <graham.whaley@intel.com>
This commit is contained in:
parent
a5436627f5
commit
2cd0c88574
31
README.md
31
README.md
@ -20,6 +20,8 @@ For details of the other Kata Containers repositories, see the
|
|||||||
* [Architecture overview](#architecture-overview)
|
* [Architecture overview](#architecture-overview)
|
||||||
* [Configuration](#configuration)
|
* [Configuration](#configuration)
|
||||||
* [Logging](#logging)
|
* [Logging](#logging)
|
||||||
|
* [Kata OCI](#kata-oci)
|
||||||
|
* [Kata containerd shimv2](#kata-containerd-shimv2)
|
||||||
* [Debugging](#debugging)
|
* [Debugging](#debugging)
|
||||||
* [Limitations](#limitations)
|
* [Limitations](#limitations)
|
||||||
* [Community](#community)
|
* [Community](#community)
|
||||||
@ -138,8 +140,17 @@ $ kata-runtime kata-env
|
|||||||
|
|
||||||
## Logging
|
## Logging
|
||||||
|
|
||||||
The runtime provides `--log=` and `--log-format=` options. However, the
|
For detailed information and analysis on obtaining logs for other system
|
||||||
runtime also always logs to the system log (`syslog` or `journald`).
|
components, see the documentation for the
|
||||||
|
[`kata-log-parser`](https://github.com/kata-containers/tests/tree/master/cmd/log-parser)
|
||||||
|
tool.
|
||||||
|
|
||||||
|
For runtime logs, see the following sections for the CRI-O and containerd shimv2 based runtimes.
|
||||||
|
|
||||||
|
### Kata OCI
|
||||||
|
|
||||||
|
The Kata OCI runtime (including when used with CRI-O), provides `--log=` and `--log-format=` options.
|
||||||
|
However, the runtime also always logs to the system log (`syslog` or `journald`).
|
||||||
|
|
||||||
To view runtime log output:
|
To view runtime log output:
|
||||||
|
|
||||||
@ -147,10 +158,18 @@ To view runtime log output:
|
|||||||
$ sudo journalctl -t kata-runtime
|
$ sudo journalctl -t kata-runtime
|
||||||
```
|
```
|
||||||
|
|
||||||
For detailed information and analysis on obtaining logs for other system
|
### Kata containerd shimv2
|
||||||
components, see the documentation for the
|
|
||||||
[`kata-log-parser`](https://github.com/kata-containers/tests/tree/master/cmd/log-parser)
|
The Kata containerd shimv2 runtime logs through `containerd`, and its logs will be sent
|
||||||
tool.
|
to wherever the `containerd` logs are directed. However, the
|
||||||
|
shimv2 runtime also always logs to the system log (`syslog` or `journald`) under the
|
||||||
|
identifier name of `kata`.
|
||||||
|
|
||||||
|
To view the `shimv2` runtime log output:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
$ sudo journalctl -t kata
|
||||||
|
```
|
||||||
|
|
||||||
## Debugging
|
## Debugging
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user