For kubeadm , kubetlet , kubectl should same version package in this lab I used v1.31 to have 1.31.7 References: Https://kubernetes.io/docs/reference/networking/ports-and-protocols/ Https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/ Https://github.com/opencontainers/runc/releases/... - Source: dev.to / over 1 year ago

Previously I wrote about the multiple variants of Docker and also the dependencies behind the Docker daemon. One of the dependencies was the container runtime called runc. That is what creates the usual containers we are all familiar with. When you use Docker, this is the default runtime, which is understandable since it was started by Docker, Inc. - Source: dev.to / almost 2 years ago

Now we have dockerd which uses containerd, but containerd will not create containers directly. It needs a runtime and the default runtime is runc, but that can be changed. Containerd actually doesn't have to know the parameters of the runtime. There is a shim process between containerd and runc, so containerd knows the parameters of the shim, and the shim knows the parameters of runc or other runtimes. - Source: dev.to / almost 2 years ago

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / almost 3 years ago

Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 3 years ago

Have you ever read any of the introductory material that the git project itself maintains for teaching how to use the tool? - https://git-scm.com/docs/gittutorial - https://git-scm.com/docs/giteveryday - https://git-scm.com/docs/gitworkflows - https://git-scm.com/docs/gitfaq - https://git-scm.com/cheat-sheet Or if you want to sit down and really learn the nuts and bolts - https://git-scm.com/book/en/v2. - Source: Hacker News / 12 days ago

I was uncomfortable with git until I read (the first 3 chapters of) the pro git book ( free here : https://git-scm.com/book/en/v2 ). It provides a great mental model of how git works under the hood. The UI of git - for better or worse - directly reflects its internals. And when I understood them, everything clicked into place. - Source: Hacker News / 24 days ago

This reminds me of a passage from the book "Pro Git". "Here’s an example to give you an idea of what it would take to get a SHA-1 collision. If all 6.5 billion humans on Earth were programming, and every second, each one was producing code that was the equivalent of the entire Linux kernel history (6.5 million Git objects) and pushing it into one enormous Git repository, it would... - Source: Hacker News / 3 months ago

If you want to go deeper into how Git actually works, the Pro Git book is the best resource out there. It is free to read online at https://git-scm.com/book/en/v2 and covers everything from basics to advanced internals. I highly recommend it if you really want to master Git. - Source: dev.to / 3 months ago

The relevant XKCD comic https://xkcd.com/1597/ FWIW I too was once a "memorised a few commands and that was it" type of dev, then I read 3 chapters of the Git book https://git-scm.com/book/en/v2 (well really two, the first chapter was a "these are things you already know") and wow did my life with git change. - Source: Hacker News / 4 months ago