I’m finally beginning to delve into containers after many years of assuming (since 2014) that containerization would be just another bygone trend in IT history. Such bad judgement on my part.
I do wish introduction articles and other related content were explained in plain English, but I know I’ll eventually understand what technical jargon DevOps people are zealously publishing online.
@stutteringsteve@twtxt.net let me explain it for you…
Containers are just Linux processes with optional different namespaces and control groups (cgroups).
Containers are normally formed with their own “root filesystem” called an OCI Image which is what tools like docker build and the Dockerfile format is good at doing. Think of this as a “chroot” really because that’s what it results in, basically an image is effectively a Tarball (actually it is with special JSON metadata).
That’s about it.
And if anyone tries to convince you that k8s is an OS and that Kubernetes is the only “container technology”, tell them to come talk to me where I’ll happily re-educate them 😂
@stutteringsteve@twtxt.net There’s a lot of info out there, obviously, but I found this blog post particularly useful when I was trying to see where Nomad and Kubernetes best fit: https://www.hashicorp.com/blog/nomad-kubernetes-a-pragmatic-look-at-choosing-orchestrators