Docker与runc有什么关系?为何Docker创建的容器无法被runc管理
容器运行时管控差异实测
根据实际环境观测,dockerd 底层流程会调用 runc 完成容器的创建动作,但Docker生态下的容器无法被系统全局安装的runc工具直接识别、管理;反观Podman创建的容器,可以被runc直接感知并纳入管控范围。
参考实测信息
Docker相关观测
完整的进程状态、命令查询输出如下:
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 4 0 1931 1 20 0 807236 90420 - Ssl ? 1:13 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock 0 0 2139 1 20 0 113116 7432 - Sl ? 0:28 /usr/bin/containerd-shim-runc-v2 -namespace moby -id 7f3fa77ddad85e82619b21d6fd9bde8c6 4 0 2163 2139 20 0 10636 6032 - Ss ? 0:00 \_ nginx: master process nginx -g daemon off; 5 101 2217 2163 20 0 11032 2560 - S ? 0:00 \_ nginx: worker process 0 0 2240 1 20 0 111964 6584 - Sl ? 0:28 /usr/bin/containerd-shim-runc-v2 -namespace moby -id 05ebb62bc6557c76f9d4494bbd2262e9f 4 0 2261 2240 20 0 10636 5988 - Ss ? 0:00 \_ nginx: master process nginx -g daemon off; 5 101 2319 2261 20 0 11032 2760 - S ? 0:00 \_ nginx: worker process $ docker container ls CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 05ebb62bc655 nginx "/docker-entrypoint.…" 6 days ago Up 6 days 80/tcp nginx2 7f3fa77ddad8 nginx "/docker-entrypoint.…" 6 days ago Up 6 days 80/tcp nginx1 $ runc list ID PID STATUS BUNDLE CREATED OWNER
输出结果显示:两个Docker运行的nginx容器能被docker container ls正常检索,但全局执行runc list没有匹配到任何容器记录。
Podman相关观测
对应环境下的完整观测输出如下:
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 1 0 128933 1 20 0 143820 2196 x64_sy Ssl ? 0:00 /usr/bin/conmon --api-version 1 -c 2d37331cea4eb213189db820840c9d3bf3f9abc4a9d92ca4225 4 0 128942 128933 20 0 10640 5980 - Ss ? 0:00 \_ nginx: master process nginx -g daemon off; 5 101 128976 128942 20 0 11036 2564 do_epo S ? 0:00 \_ nginx: worker process 1 0 129276 1 20 0 143820 2324 x64_sy Ssl ? 0:00 /usr/bin/conmon --api-version 1 -c 2bf3a1f5fdd479cf1402984322f9d09a2b22149d6f01d776049 4 0 129285 129276 20 0 10640 5940 - Ss ? 0:00 \_ nginx: master process nginx -g daemon off; 5 101 129320 129285 20 0 11036 2632 do_epo S ? 0:00 \_ nginx: worker process ❯ podman container ls CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 2bf3a1f5fdd4 docker.io/library/nginx:latest nginx -g daemon o... 6 days ago Up 6 days ago nginx1 2d37331cea4e docker.io/library/nginx:latest nginx -g daemon o... 6 days ago Up 6 days ago nginx2 ❯ runc list ID PID STATUS BUNDLE CREATED OWNER 2bf3a1f5fdd479cf1402984322f9d09a2b22149d6f01d7760493e482253ed2c3 129285 running /var/lib/containers/storage/overlay-containers/2bf3a1f5fdd479cf1402984322f9d09a2b22149d6f01d7760493e482253ed2c3/userdata 2021-03-17T08:04:13.948219157Z root 2d37331cea4eb213189db820840c9d3bf3f9abc4a9d92ca42253520cbe2b6710 128942 running /var/lib/containers/storage/overlay-containers/2d37331cea4eb213189db820840c9d3bf3f9abc4a9d92ca42253520cbe2b6710/userdata 2021-03-17T08:03:40.961730347Z root
输出结果显示:两个Podman管理的nginx容器,既可以被podman container ls正常检索,也能被全局runc list完整识别,容器ID、进程PID、存储路径等信息全部一一对应。
内容的提问来源于stack exchange,提问作者Mystic
相关产品推荐
相关产品推荐

