https://asoldatenko.org/categories/ephemeral/Recent content in Ephemeral on Personal BlogHugo -- gohugo.ioen-gbThu, 23 Jul 2026 19:07:45 +0200https://asoldatenko.org/posts/custom-debug-containers/Thu, 23 Jul 2026 19:07:45 +0200https://asoldatenko.org/posts/custom-debug-containers/Intro In my previous post, I wrote about how to run a debug ephemeral container to troubleshoot distroless images in Kubernetes. I also mentioned that we can use a custom image to override a distroless image, allowing us to run specific troubleshooting tools. In this post, I will demonstrate how to set up a custom debug container and explain why it is beneficial to do so. Problem Assuming we want to debug an issue within a Kubernetes cluster, we generally have two options:https://asoldatenko.org/posts/debug-distroless-images-on-k8s/Sun, 19 Jul 2026 18:46:11 +0200https://asoldatenko.org/posts/debug-distroless-images-on-k8s/Define a problem: Sometimes we want to attach to a running pod and troubleshoot something from there. But it requires that image which container inside pod is running includes some tools we need ( atleast shell, and some basic linux tools: cat, grep etc. ) How to debug k8s? The first simple idea that came to mind is to run kubectl exec -it <pod-name> - sh. And if it includes shell we can navigate and do some basic checks for example ping, or check if we have permissions to create or modify files etc.