<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Amd on Personal Blog</title><link>https://asoldatenko.org/categories/amd/</link><description>Recent content in Amd on Personal Blog</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Thu, 23 Jul 2026 19:07:45 +0200</lastBuildDate><atom:link href="https://asoldatenko.org/categories/amd/index.xml" rel="self" type="application/rss+xml"/><item><title>Custom Debug Containers</title><link>https://asoldatenko.org/posts/custom-debug-containers/</link><pubDate>Thu, 23 Jul 2026 19:07:45 +0200</pubDate><guid>https://asoldatenko.org/posts/custom-debug-containers/</guid><description>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:</description></item></channel></rss>