> I'm still stuck at the 'I don't get it' phase, despite looking at Docker, and more recently Kubernetes, several times over the years, mainly because everyone

> I'm still stuck at the 'I don't get it' phase, despite looking at Docker, and more recently Kubernetes, several times over the years, mainly because everyone around me evangelizes it so much. Docker is a reimplementation of binary packages, except it pulls in whole operating system (as a chroot image) as a dependency instead of finer granularity and provides separate networking for each package, so every service running on a single server can be statically bound to 192.168.56.16:8888, even though the server never saw the 192.168.56.0/24 network. All that at the cost of quite opaque heavy magic with filesystems and network configuration. Kubernetes is a reiteration of configuration management software, this time with Docker replacing RPMs and DEBs, and a failure detection mechanism that can install and start a failed package (service) on some other server in the network. More or less.