Installing Containerd
Two ways to get containerd onto a host: from a YUM repo, or by unpacking the official binary tarball. Both cover where the files land, how the systemd unit is wired up, and the runtime settings that are easy to get wrong.
Chapters
About this series
The same goal — getting the containerd runtime running on a host — was reached two ways: installing the package a distribution ships through its YUM repo, and unpacking the official binary tarball and placing each file by hand.
Both are kept because the trade-off differs. The YUM route is fast and upgrades come with the repo, but the version is whatever the repo offers. The binary route lets you pick a version and makes it obvious where every file goes, at the cost of wiring each piece up yourself. Read both, and you can judge which one fits your environment.