Dockershim and some network tips - 123dev #66
Posted on April 5, 2022 • 2 minutes • 376 words
Facts don’t convince people.
You don’t have to change someone’s mind. You just need to give them doubts about what they know.
“Statistics should be the driest thing” – Florence Nightingale
From How to Lie with Statistics
You need to learn how to tell stories, not data.
So much to learn
In writing the detector for docker socket plugin I had a co-worker review it with me. They are a much better developer than I am. I can make things work, but it’s often not idiomatic and many times not clean.
In a 30 minute call with them I learned a lot. I also learned a small bit more about what I don’t know (and need to learn more about).
I love when that happens. When someone opens the door to more knowledge that is hard to gain without experience.
Learn from the experiences of others to understand the things data cannot teach you.
Here’s a project I spent some time on at work. It makes it easy for you to know if any workloads in a Kubernetes cluster are mounting the docker socket. It’s now open source and available as a
Running this on your cluster or manifest files should give you confidence to change your container runtime and upgrade to Kubernetes 1.24 once it is released.
GitHub - aws-containers/kubectl-detector-for-docker-socket — github.com
A Kubectl plugin that can detect if any of your workloads or manifest files are mounting the docker.sock volume.
I didn’t know it was possible to to save your decryption keys in plain text. Extremely useful—and no surprise—that wireshark supports it.
Decrypting your own HTTPS traffic with Wireshark – Trickster Dev Code level discussion of web scraping, gray hat automation, growth hacking and bounty hunting
I like it when people take the time to explain the output from commands and how you should read the data. It’s a way to learn from other people’s experience.
I also didn’t know the difference between
mtr so this was particularly insightful to know I should be using mtr instead.
How to properly interpret a traceroute or mtr — phil.lavin.me.uk traceroute vs mtr When a packet travels across the Internet, it travels through multiple routers. The traceroute and mtr tools