578 lines
19 KiB
Markdown
578 lines
19 KiB
Markdown
---
|
||
reviewers:
|
||
- Random-Liu
|
||
- feiskyer
|
||
- mrunalp
|
||
title: 使用 crictl 对 Kubernetes 节点进行调试
|
||
content_type: task
|
||
---
|
||
|
||
<!--
|
||
reviewers:
|
||
- Random-Liu
|
||
- feiskyer
|
||
- mrunalp
|
||
title: Debugging Kubernetes nodes with crictl
|
||
content_type: task
|
||
-->
|
||
|
||
|
||
<!-- overview -->
|
||
|
||
{{< feature-state for_k8s_version="v1.11" state="stable" >}}
|
||
|
||
<!--
|
||
`crictl` is a command-line interface for CRI-compatible container runtimes.
|
||
You can use it to inspect and debug container runtimes and applications on a
|
||
Kubernetes node. `crictl` and its source are hosted in the
|
||
[cri-tools](https://github.com/kubernetes-sigs/cri-tools) repository.
|
||
-->
|
||
|
||
`crictl` 是 CRI 兼容的容器运行时命令行接口。
|
||
你可以使用它来检查和调试 Kubernetes 节点上的容器运行时和应用程序。
|
||
`crictl` 和它的源代码在
|
||
[cri-tools](https://github.com/kubernetes-sigs/cri-tools) 代码库。
|
||
|
||
## {{% heading "prerequisites" %}}
|
||
|
||
<!--
|
||
`crictl` requires a Linux operating system with a CRI runtime.
|
||
-->
|
||
`crictl` 需要带有 CRI 运行时的 Linux 操作系统。
|
||
|
||
<!-- steps -->
|
||
|
||
<!--
|
||
## Installing crictl
|
||
|
||
You can download a compressed archive `crictl` from the cri-tools [release
|
||
page](https://github.com/kubernetes-sigs/cri-tools/releases), for several
|
||
different architectures. Download the version that corresponds to your version
|
||
of Kubernetes. Extract it and move it to a location on your system path, such as
|
||
`/usr/local/bin/`.
|
||
-->
|
||
## 安装 crictl
|
||
|
||
你可以从 cri-tools [发布页面](https://github.com/kubernetes-sigs/cri-tools/releases)
|
||
下载一个压缩的 `crictl` 归档文件，用于几种不同的架构。
|
||
下载与你的 kubernetes 版本相对应的版本。
|
||
提取它并将其移动到系统路径上的某个位置，例如`/usr/local/bin/`。
|
||
|
||
<!--
|
||
## General usage
|
||
|
||
The `crictl` command has several subcommands and runtime flags. Use
|
||
`crictl help` or `crictl <subcommand> help` for more details.
|
||
-->
|
||
## 一般用法
|
||
|
||
`crictl` 命令有几个子命令和运行时参数。
|
||
有关详细信息，请使用 `crictl help` 或 `crictl <subcommand> help` 获取帮助信息。
|
||
|
||
<!--
|
||
`crictl` connects to `unix:///var/run/dockershim.sock` by default. For other
|
||
runtimes, you can set the endpoint in multiple different ways:
|
||
-->
|
||
`crictl` 默认连接到 `unix:///var/run/dockershim.sock`。
|
||
对于其他的运行时，你可以用多种不同的方法设置端点：
|
||
|
||
<!--
|
||
- By setting flags `--runtime-endpoint` and `--image-endpoint`
|
||
- By setting environment variables `CONTAINER_RUNTIME_ENDPOINT` and `IMAGE_SERVICE_ENDPOINT`
|
||
- By setting the endpoint in the config file `--config=/etc/crictl.yaml`
|
||
-->
|
||
- 通过设置参数 `--runtime-endpoint` 和 `--image-endpoint`
|
||
- 通过设置环境变量 `CONTAINER_RUNTIME_ENDPOINT` 和 `IMAGE_SERVICE_ENDPOINT`
|
||
- 通过在配置文件中设置端点 `--config=/etc/crictl.yaml`
|
||
|
||
<!--
|
||
You can also specify timeout values when connecting to the server and enable or
|
||
disable debugging, by specifying `timeout` or `debug` values in the configuration
|
||
file or using the `--timeout` and `--debug` command-line flags.
|
||
-->
|
||
你还可以在连接到服务器并启用或禁用调试时指定超时值，方法是在配置文件中指定
|
||
`timeout` 或 `debug` 值，或者使用 `--timeout` 和 `--debug` 命令行参数。
|
||
|
||
<!--
|
||
To view or edit the current configuration, view or edit the contents of
|
||
`/etc/crictl.yaml`.
|
||
-->
|
||
要查看或编辑当前配置，请查看或编辑 `/etc/crictl.yaml` 的内容。
|
||
|
||
```shell
|
||
cat /etc/crictl.yaml
|
||
```
|
||
```
|
||
runtime-endpoint: unix:///var/run/dockershim.sock
|
||
image-endpoint: unix:///var/run/dockershim.sock
|
||
timeout: 10
|
||
debug: true
|
||
```
|
||
|
||
<!--
|
||
## Example crictl commands
|
||
|
||
The following examples show some `crictl` commands and example output.
|
||
-->
|
||
## crictl 命令示例
|
||
|
||
{{< warning >}}
|
||
<!--
|
||
If you use `crictl` to create pod sandboxes or containers on a running
|
||
Kubernetes cluster, the Kubelet will eventually delete them. `crictl` is not a
|
||
general purpose workflow tool, but a tool that is useful for debugging.
|
||
-->
|
||
如果使用 `crictl` 在正在运行的 Kubernetes 集群上创建 Pod 沙盒或容器，
|
||
kubelet 最终将删除它们。
|
||
`crictl` 不是一个通用的工作流工具，而是一个对调试有用的工具。
|
||
{{< /warning >}}
|
||
|
||
<!--
|
||
### List pods
|
||
|
||
List all pods:
|
||
-->
|
||
### 打印 Pod 清单
|
||
|
||
打印所有 Pod 的清单：
|
||
|
||
```shell
|
||
crictl pods
|
||
```
|
||
|
||
```none
|
||
POD ID CREATED STATE NAME NAMESPACE ATTEMPT
|
||
926f1b5a1d33a About a minute ago Ready sh-84d7dcf559-4r2gq default 0
|
||
4dccb216c4adb About a minute ago Ready nginx-65899c769f-wv2gp default 0
|
||
a86316e96fa89 17 hours ago Ready kube-proxy-gblk4 kube-system 0
|
||
919630b8f81f1 17 hours ago Ready nvidia-device-plugin-zgbbv kube-system 0
|
||
```
|
||
|
||
<!--
|
||
List pods by name:
|
||
-->
|
||
根据名称打印 Pod 清单：
|
||
|
||
```shell
|
||
crictl pods --name nginx-65899c769f-wv2gp
|
||
```
|
||
|
||
```none
|
||
POD ID CREATED STATE NAME NAMESPACE ATTEMPT
|
||
4dccb216c4adb 2 minutes ago Ready nginx-65899c769f-wv2gp default 0
|
||
```
|
||
|
||
<!--
|
||
List pods by label:
|
||
-->
|
||
根据标签打印 Pod 清单：
|
||
|
||
```shell
|
||
crictl pods --label run=nginx
|
||
```
|
||
```none
|
||
POD ID CREATED STATE NAME NAMESPACE ATTEMPT
|
||
4dccb216c4adb 2 minutes ago Ready nginx-65899c769f-wv2gp default 0
|
||
```
|
||
|
||
<!--
|
||
### List images
|
||
|
||
List all images:
|
||
-->
|
||
### 打印镜像清单
|
||
|
||
打印所有镜像清单：
|
||
|
||
```shell
|
||
crictl images
|
||
```
|
||
```none
|
||
IMAGE TAG IMAGE ID SIZE
|
||
busybox latest 8c811b4aec35f 1.15MB
|
||
k8s-gcrio.azureedge.net/hyperkube-amd64 v1.10.3 e179bbfe5d238 665MB
|
||
k8s-gcrio.azureedge.net/pause-amd64 3.1 da86e6ba6ca19 742kB
|
||
nginx latest cd5239a0906a6 109MB
|
||
```
|
||
|
||
<!--
|
||
List images by repository:
|
||
-->
|
||
根据仓库打印镜像清单：
|
||
|
||
```shell
|
||
crictl images nginx
|
||
```
|
||
```none
|
||
IMAGE TAG IMAGE ID SIZE
|
||
nginx latest cd5239a0906a6 109MB
|
||
```
|
||
|
||
<!--
|
||
Only list image IDs:
|
||
-->
|
||
只打印镜像 ID：
|
||
|
||
```shell
|
||
crictl images -q
|
||
```
|
||
```none
|
||
sha256:8c811b4aec35f259572d0f79207bc0678df4c736eeec50bc9fec37ed936a472a
|
||
sha256:e179bbfe5d238de6069f3b03fccbecc3fb4f2019af741bfff1233c4d7b2970c5
|
||
sha256:da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e
|
||
sha256:cd5239a0906a6ccf0562354852fae04bc5b52d72a2aff9a871ddb6bd57553569
|
||
```
|
||
|
||
<!--
|
||
### List containers
|
||
|
||
List all containers:
|
||
-->
|
||
### 打印容器清单
|
||
|
||
打印所有容器清单：
|
||
|
||
```shell
|
||
crictl ps -a
|
||
```
|
||
```none
|
||
CONTAINER ID IMAGE CREATED STATE NAME ATTEMPT
|
||
1f73f2d81bf98 busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 7 minutes ago Running sh 1
|
||
9c5951df22c78 busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 8 minutes ago Exited sh 0
|
||
87d3992f84f74 nginx@sha256:d0a8828cccb73397acb0073bf34f4d7d8aa315263f1e7806bf8c55d8ac139d5f 8 minutes ago Running nginx 0
|
||
1941fb4da154f k8s-gcrio.azureedge.net/hyperkube-amd64@sha256:00d814b1f7763f4ab5be80c58e98140dfc69df107f253d7fdd714b30a714260a 18 hours ago Running kube-proxy 0
|
||
```
|
||
|
||
<!--
|
||
List running containers:
|
||
-->
|
||
打印正在运行的容器清单：
|
||
|
||
```shell
|
||
crictl ps
|
||
```
|
||
```none
|
||
CONTAINER ID IMAGE CREATED STATE NAME ATTEMPT
|
||
1f73f2d81bf98 busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 6 minutes ago Running sh 1
|
||
87d3992f84f74 nginx@sha256:d0a8828cccb73397acb0073bf34f4d7d8aa315263f1e7806bf8c55d8ac139d5f 7 minutes ago Running nginx 0
|
||
1941fb4da154f k8s-gcrio.azureedge.net/hyperkube-amd64@sha256:00d814b1f7763f4ab5be80c58e98140dfc69df107f253d7fdd714b30a714260a 17 hours ago Running kube-proxy 0
|
||
```
|
||
|
||
<!--
|
||
### Execute a command in a running container
|
||
-->
|
||
### 在正在运行的容器上执行命令
|
||
|
||
```shell
|
||
crictl exec -i -t 1f73f2d81bf98 ls
|
||
```
|
||
```none
|
||
bin dev etc home proc root sys tmp usr var
|
||
```
|
||
|
||
<!--
|
||
### Get a container's logs
|
||
|
||
Get all container logs:
|
||
-->
|
||
### 获取容器日志
|
||
|
||
获取容器的所有日志：
|
||
|
||
```shell
|
||
crictl logs 87d3992f84f74
|
||
```
|
||
```none
|
||
10.240.0.96 - - [06/Jun/2018:02:45:49 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.47.0" "-"
|
||
10.240.0.96 - - [06/Jun/2018:02:45:50 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.47.0" "-"
|
||
10.240.0.96 - - [06/Jun/2018:02:45:51 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.47.0" "-"
|
||
```
|
||
|
||
<!--
|
||
Get only the latest `N` lines of logs:
|
||
-->
|
||
获取最近的 `N` 行日志：
|
||
|
||
```shell
|
||
crictl logs --tail=1 87d3992f84f74
|
||
```
|
||
```none
|
||
10.240.0.96 - - [06/Jun/2018:02:45:51 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.47.0" "-"
|
||
```
|
||
|
||
<!--
|
||
### Run a pod sandbox
|
||
|
||
Using `crictl` to run a pod sandbox is useful for debugging container runtimes.
|
||
On a running Kubernetes cluster, the sandbox will eventually be stopped and
|
||
deleted by the Kubelet.
|
||
-->
|
||
### 运行 Pod 沙盒
|
||
|
||
用 `crictl` 运行 Pod 沙盒对容器运行时排错很有帮助。
|
||
在运行的 Kubernetes 集群中，沙盒会随机地被 kubelet 停止和删除。
|
||
|
||
1. <!--Create a JSON file like the following:-->
|
||
编写下面的 JSON 文件：
|
||
|
||
```json
|
||
{
|
||
"metadata": {
|
||
"name": "nginx-sandbox",
|
||
"namespace": "default",
|
||
"attempt": 1,
|
||
"uid": "hdishd83djaidwnduwk28bcsb"
|
||
},
|
||
"logDirectory": "/tmp",
|
||
"linux": {
|
||
}
|
||
}
|
||
```
|
||
|
||
2. <!--Use the `crictl runp` command to apply the JSON and run the sandbox.-->
|
||
使用 `crictl runp` 命令应用 JSON 文件并运行沙盒。
|
||
|
||
```shell
|
||
crictl runp pod-config.json
|
||
```
|
||
|
||
<!--The ID of the sandbox is returned.-->
|
||
返回了沙盒的 ID。
|
||
|
||
<!--
|
||
### Create a container
|
||
|
||
Using `crictl` to create a container is useful for debugging container runtimes.
|
||
On a running Kubernetes cluster, the sandbox will eventually be stopped and
|
||
deleted by the Kubelet.
|
||
-->
|
||
### 创建容器
|
||
|
||
用 `crictl` 创建容器对容器运行时排错很有帮助。
|
||
在运行的 Kubernetes 集群中，沙盒会随机的被 kubelet 停止和删除。
|
||
|
||
1. <!--Pull a busybox image-->
|
||
拉取 busybox 镜像
|
||
|
||
```bash
|
||
crictl pull busybox
|
||
Image is up to date for busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47
|
||
```
|
||
|
||
2. <!--Create configs for the pod and the container:-->
|
||
创建 Pod 和容器的配置：
|
||
|
||
<!--**Pod config**:-->
|
||
**Pod 配置**：
|
||
```yaml
|
||
{
|
||
"metadata": {
|
||
"name": "nginx-sandbox",
|
||
"namespace": "default",
|
||
"attempt": 1,
|
||
"uid": "hdishd83djaidwnduwk28bcsb"
|
||
},
|
||
"log_directory": "/tmp",
|
||
"linux": {
|
||
}
|
||
}
|
||
```
|
||
|
||
<!--**Container config**:-->
|
||
**容器配置**：
|
||
```yaml
|
||
{
|
||
"metadata": {
|
||
"name": "busybox"
|
||
},
|
||
"image":{
|
||
"image": "busybox"
|
||
},
|
||
"command": [
|
||
"top"
|
||
],
|
||
"log_path":"busybox.log",
|
||
"linux": {
|
||
}
|
||
}
|
||
```
|
||
|
||
3. <!--Create the container, passing the ID of the previously-created pod, the
|
||
container config file, and the pod config file. The ID of the container is
|
||
returned.-->
|
||
创建容器，传递先前创建的 Pod 的 ID、容器配置文件和 Pod 配置文件。返回容器的 ID。
|
||
|
||
```bash
|
||
crictl create f84dd361f8dc51518ed291fbadd6db537b0496536c1d2d6c05ff943ce8c9a54f container-config.json pod-config.json
|
||
```
|
||
|
||
4. <!--List all containers and verify that the newly-created container has its
|
||
state set to `Created`.-->
|
||
查询所有容器并确认新创建的容器状态为 `Created`。
|
||
|
||
```bash
|
||
crictl ps -a
|
||
```
|
||
```none
|
||
CONTAINER ID IMAGE CREATED STATE NAME ATTEMPT
|
||
3e025dd50a72d busybox 32 seconds ago Created busybox 0
|
||
```
|
||
|
||
<!--
|
||
### Start a container
|
||
|
||
To start a container, pass its ID to `crictl start`:
|
||
-->
|
||
### 启动容器
|
||
|
||
要启动容器，要将容器 ID 传给 `crictl start`：
|
||
|
||
```shell
|
||
crictl start 3e025dd50a72d956c4f14881fbb5b1080c9275674e95fb67f965f6478a957d60
|
||
```
|
||
```none
|
||
3e025dd50a72d956c4f14881fbb5b1080c9275674e95fb67f965f6478a957d60
|
||
```
|
||
|
||
<!--
|
||
Check the container has its state set to `Running`.
|
||
-->
|
||
确认容器的状态为 `Running`。
|
||
|
||
```shell
|
||
crictl ps
|
||
```
|
||
```none
|
||
CONTAINER ID IMAGE CREATED STATE NAME ATTEMPT
|
||
3e025dd50a72d busybox About a minute ago Running busybox 0
|
||
```
|
||
<!-- discussion -->
|
||
|
||
<!--
|
||
See [kubernetes-sigs/cri-tools](https://github.com/kubernetes-sigs/cri-tools)
|
||
for more information.
|
||
-->
|
||
更多信息请参考 [kubernetes-sigs/cri-tools](https://github.com/kubernetes-sigs/cri-tools)。
|
||
|
||
<!--
|
||
## Mapping from docker cli to crictl
|
||
-->
|
||
## Docker CLI 和 crictl 的映射
|
||
|
||
<!--
|
||
The exact versions for below mapping table are for docker cli v1.40 and crictl v1.19.0. Please note that the list is not exhaustive. For example, it doesn't include experimental commands of docker cli.
|
||
-->
|
||
以下的映射表格只适用于 Docker CLI v1.40 和 crictl v1.19.0 版本。
|
||
请注意该表格并不详尽。例如，其中不包含 Docker CLI 的实验性命令。
|
||
|
||
<!--
|
||
{{< note >}}
|
||
The output format of CRICTL is similar to Docker CLI, despite some missing columns for some CLI. Make sure to check output for the specific command if your script output parsing.
|
||
{{< /note >}}
|
||
-->
|
||
{{< note >}}
|
||
尽管有些命令的输出缺少了一些数据列，CRICTL 的输出格式与 Docker CLI 是类似的。
|
||
如果你的脚本程序需要解析命令的输出，请确认检查该特定命令的输出。
|
||
{{< /note >}}
|
||
|
||
<!--
|
||
### Retrieve Debugging Information
|
||
|
||
{{< table caption="mapping from docker cli to crictl - retrieve debugging information" >}}
|
||
-->
|
||
### 获取调试信息
|
||
|
||
{{< table caption="Docker CLI 和 crictl 的映射 - 获取调试信息" >}}
|
||
<!--
|
||
docker cli | crictl | Description | Unsupported Features
|
||
-- | -- | -- | --
|
||
`attach` | `attach` | Attach to a running container | `--detach-keys`, `--sig-proxy`
|
||
`exec` | `exec` | Run a command in a running container | `--privileged`, `--user`, `--detach-keys`
|
||
`images` | `images` | List images |
|
||
`info` | `info` | Display system-wide information |
|
||
`inspect` | `inspect`, `inspecti` | Return low-level information on a container, image or task |
|
||
`logs` | `logs` | Fetch the logs of a container | `--details`
|
||
`ps` | `ps` | List containers |
|
||
`stats` | `stats` | Display a live stream of container(s) resource usage statistics | Column: NET/BLOCK I/O, PIDs
|
||
`version` | `version` | Show the runtime (Docker, ContainerD, or others) version information |
|
||
{{< /table >}}
|
||
-->
|
||
docker cli | crictl | 描述 | 不支持的功能
|
||
-- | -- | -- | --
|
||
`attach` | `attach` | 连接到一个运行中的容器 | `--detach-keys`, `--sig-proxy`
|
||
`exec` | `exec` | 在运行中的容器里运行一个命令 | `--privileged`, `--user`, `--detach-keys`
|
||
`images` | `images` | 列举镜像 |
|
||
`info` | `info` | 显示系统级的信息 |
|
||
`inspect` | `inspect`, `inspecti` | 返回容器、镜像或者任务的详细信息 |
|
||
`logs` | `logs` | 获取容器的日志 | `--details`
|
||
`ps` | `ps` | 列举容器 |
|
||
`stats` | `stats` | 实时显示容器的资源使用统计信息 | 列：NET/BLOCK I/O, PIDs
|
||
`version` | `version` | 显示运行时（Docker、ContainerD、或者其他) 的版本信息 |
|
||
{{< /table >}}
|
||
|
||
<!--
|
||
### Perform Changes
|
||
|
||
{{< table caption="mapping from docker cli to crictl - perform changes" >}}
|
||
-->
|
||
### 进行改动
|
||
|
||
{{< table caption="Docker CLI 和 crictl 的映射 - 进行改动" >}}
|
||
<!--
|
||
docker cli | crictl | Description | Unsupported Features
|
||
-- | -- | -- | --
|
||
`create` | `create` | Create a new container |
|
||
`kill` | `stop` (timeout = 0) | Kill one or more running container | `--signal`
|
||
`pull` | `pull` | Pull an image or a repository from a registry | `--all-tags`, `--disable-content-trust`
|
||
`rm` | `rm` | Remove one or more containers |
|
||
`rmi` | `rmi` | Remove one or more images |
|
||
`run` | `run` | Run a command in a new container |
|
||
`start` | `start` | Start one or more stopped containers | `--detach-keys`
|
||
`stop` | `stop` | Stop one or more running containers |
|
||
`update` | `update` | Update configuration of one or more containers | `--restart`, `--blkio-weight` and some other resource limit not supported by CRI.
|
||
{{< /table >}}
|
||
-->
|
||
docker cli | crictl | 描述 | 不支持的功能
|
||
-- | -- | -- | --
|
||
`create` | `create` | 创建一个新的容器 |
|
||
`kill` | `stop` (timeout=0) | 杀死一个或多个正在运行的容器 | `--signal`
|
||
`pull` | `pull` | 从镜像仓库拉取镜像或者代码仓库 | `--all-tags`, `--disable-content-trust`
|
||
`rm` | `rm` | 移除一个或多个容器 |
|
||
`rmi` | `rmi` | 移除一个或多个镜像 |
|
||
`run` | `run` | 在新容器里运行一个命令 |
|
||
`start` | `start` | 启动一个或多个停止的容器 | `--detach-keys`
|
||
`stop` | `stop` | 停止一个或多个正运行的容器 |
|
||
`update` | `update` | 更新一个或多个容器的配置 | CRI 不支持 `--restart`、`--blkio-weight` 以及一些其他的资源限制选项。
|
||
{{< /table >}}
|
||
|
||
<!--
|
||
### Supported only in crictl
|
||
|
||
{{< table caption="mapping from docker cli to crictl - supported only in crictl" >}}
|
||
-->
|
||
### 仅 crictl 支持
|
||
|
||
{{< table caption="Docker CLI 和 crictl 的映射 - 仅 crictl 支持" >}}
|
||
<!--
|
||
crictl | Description
|
||
-- | --
|
||
`imagefsinfo` | Return image filesystem info
|
||
`inspectp` | Display the status of one or more pods
|
||
`port-forward` | Forward local port to a pod
|
||
`pods` | List pods
|
||
`runp` | Run a new pod
|
||
`rmp` | Remove one or more pods
|
||
`stopp` | Stop one or more running pods
|
||
{{< /table >}}
|
||
-->
|
||
crictl | 描述
|
||
-- | --
|
||
`imagefsinfo` | 返回镜像的文件系统信息
|
||
`inspectp` | 显示一个或多个 Pod 的状态
|
||
`port-forward` | 转发本地端口到 Pod
|
||
`pods` | 列举 Pod
|
||
`runp` | 运行一个新的 Pod
|
||
`rmp` | 移除一个或多个 Pod
|
||
`stopp` | 停止一个或多个正运行的 Pod
|
||
{{< /table >}}
|