CR only runs single containers. Pods can hold more than one container. A pod is a shared-namespace and administrative domain that is intended to hold a single 'main' service in a single container with a number of supporting containers running alongside it. The pod is a little more than a virtual construct though, as its existence results in physical changes in name resolution, routing tables, storage, and the like.
A pod though may have many instances that run on one or more nodes. A node can be thought of as a physical computer, though often it's a VM.
Things get more complicated when looking at KinD (Kubernetes in Docker) type solutions, such as KinD itself, or K3D, where you're running the kubernetes control-plane and all of the nodes themselves as containers. In this case, things are a bit 'inception' like, but for the most part, they are modelled exactly as normal kubernetes and you can ignore the strangeness and assume that you're not really inside docker (or any other container runtime) and just work with the concepts.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…