containerd/nerdctl: README-based editorial guide

containerd/nerdctl describes itself in the README as "contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "nerdctl: Docker-compatible CLI for containerd", the README says: nerdctl is a Docker-compatible CLI for containerd.. That establishes the project's stated boundary, not a production test.

The README's "Install" section gives a useful starting point for deciding whether the project fits: RootlessKit needs to be v0.10.0 or later. v3.0.0 or later is recommended.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: v0.11.0 or later is highly recommended. Some features, such as pruning caches with nerdctl system prune, do not work with older versions.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "nerdctl: Docker-compatible CLI for containerd". The source evidence includes: ✅ [Optional] Supports rootless mode, without slirp overhead (bypass4netns). This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: # nerdctl compose -f ./examples/compose-wordpress/docker-compose.yaml up When the README contains no runnable command, this article does not invent one. Open its "Examples" section and confirm system dependencies, default ports, and first-run initialization before using a public server.