A Docker container starts with a single command, but that command has to be turned into a running Linux process. Here is what actually happens.
Good one 👍
Good visual on the daemon/containerd split. Worth calling out too that most of what people call Docker overhead is actually the image pull and layer caching, not the runtime itself once the container is actually running.
thanks for the explanation 🌈
Very nice
Good one 👍
Good visual on the daemon/containerd split. Worth calling out too that most of what people call Docker overhead is actually the image pull and layer caching, not the runtime itself once the container is actually running.
thanks for the explanation 🌈
Very nice