Containerd-shim

containerd-shim -namespace moby

http://alexander.holbreich.org/docker-components-explained/ The shim allows for daemonless containers. According to Michael Crosby it's basically sits as the parent of the container's process to facilitate a few things.

First it allows the runtimes, i.e. runc,to exit after it starts the container. This way we don't have to have the long running runtime processes for containers. Second it keeps the STDIO and other fds open for the container in case containerd and/or docker both die. If the shim was not running then the parent side of the pipes or the TTY master would be closed and the container would exit. Finally it allows the container's exit status to be reported back to a higher level tool like docker without having the be the actual parent of the container's process and do a wait4.

See also

• containerd, config.toml, containerd-shim, runc, journalctl -u containerd, ctr, SOCI Snapshotter, Containerd versions
• Docker: docker-compose, Docker Desktop, Docker Scout, Docker Swarm, Docker Volumes, Docker images management, docker network, docker inspect, docker volume inspect, Dockerfile, Docker Engine release notes,docker kill, moby, Docker-in-Docker, docker context, buildx, docker tag, docker system prune, Docker Hub, hub-tool, /etc/docker/daemon.json, hostconfig.json, dockerd, logs, Docker logging, Backup, docker service, depends on, --dns, --filter, --mount, docker login, docker build, apt remove docker.io, .dockerignore, docker context ls | docker-machine, .docker/, PWD, $HOME/.docker/config.json, Docker ID, --env-file, docker --help