How to run a "sidecar" container in the namespace(s) of another container? 🧙‍♂️ This magic trick is widely used by various container debugging tools (e.g., docker debug, cdebug exec) and even Kubernetes (to implement pods). Learn more about it at labs.iximiuz.com/challenges/…

Thanks to Claude Code, I finally found time for cdebug - the new v0.0.19 release includes K8s OIDC support and a massive dependency upgrade github.com/iximiuz/cdebug/re…

And for those who are lazy (I am :-)) you can use the 'debug' command in #DockerSlim (aka MinToolkit), which will do this for Podman, ContainerD, Kubernetes and Docker or use the dedicated 'cdebug' app Ivan created.

I haven't been keeping a close eye on it, but it turns out cdebug has been steadily growing on GitHub! It's feature-complete, so if you're tackling a tricky container debugging issue, I've got a tool for you 😎 github.com/iximiuz/cdebug

From the isolation standpoint, yes. However, containers were invented to slice large servers into tens or hundreds of smaller machines, so it's kinda given that there is more than one container per server. From the ops standpoint, it's even trickier - there is a lot of tools and services on the market to run, monitor, and debug containers. Docker (OCI) containers is the de facto standard runtime and packaging format, so it's much easier to operate them. Today, you can even exec into distroless containers with `kubectl debug` (or my own `cdebug` tool). In contrast, from my standpoint, unikernels look like black boxes that you launch and prey they behave well. The unikernel ecosystem needs to mature a little bit more before I'd consider it as a container alternative. There are, of course, situations when I'd go with a unikernel-packaged app even today. For instance, if I needed a scalable to zero but still very low latency app and I wouldn't be concerned that it might not work well with a trimmed-down kernel, I might consider deploying it as a unikernel. In other words, the upsides of this solution should outweigh the (sizeable) downsides of using a non-mainstream tech.

Debugging Distroless Images with kubectl and cdebug Read more: dev.to/chainguard/debugging-…

cdebug is a swiss army knife of container debugging: - Troubleshoot containers lacking shell - Forward unpublished or even localhost ports to your host system - Expose endpoints from the host system to containers & Kubernetes networks ➤ github.com/iximiuz/cdebug

Debugging Kubernetes pods is challenging. Debugging pods without a shell inside is next to impossible. But only if you don't have the right skills 😎 There are tools like "kubectl debug" (official) and "cdebug" (by truly yours), but the only thing that actually matters at the end of the day is your experience. The more failing pods you've troubleshooted in the past, the more confident you'll be fixing the next one. So, I prepared a few challenges to help you practice! Have fun labs.iximiuz.com/challenges?…

Use cdebug

4. cdebug - a swiss army knife of container debugging A handy tool to improve the debugging UX: - Troubleshoot containers and Pods w/o shell - Exec into unprivileged and non-root Pods - Access unpublished or even localhost ports ...and more! github.com/iximiuz/cdebug

cdebug is a swiss army knife of container debugging: - Troubleshoot containers lacking shell - Forward unpublished or even localhost ports to your host system - Expose endpoints from the host system to containers & Kubernetes networks ➜ github.com/iximiuz/cdebug

We're live with @matiaspan26 Daggerizing the World! Today we'll focus on adding @containerd support to @iximiuz 's cdebug project . Join us and ask any questions about @dagger_io you might have! x.com/i/broadcasts/1DXxydmEe…

Awesome stuff! Thank you, folks, for giving cdebug some love!

We've successfully Daggerized @iximiuz's cdebug project with @matiaspan26 . We leveraged Daggerverse modules and showcased the awesomeness of the `terminal` @dagger_io troubleshooting capability. PR below and keep tuned next Friday for more progress! github.com/iximiuz/cdebug/pu…

In today's @dagger_io "daggerize the world" stream we'll be looking forward to improve @iximiuz's cdebug project. github.com/iximiuz/cdebug Stream starts in 1 hour. You can follow this account to get notified when the stream starts.

cdebug is a swiss army knife of container debugging: - Troubleshoot containers lacking shell - Forward unpublished or even localhost ports to your host system - Expose endpoints from the host system to containers & Kubernetes networks ➤ github.com/iximiuz/cdebug

Interesting blog post about debugging distroless @chainguard_dev images but also great discovery about @iximiuz cdebug tool 💪 github.com/iximiuz/cdebug

cdebug link github.com/iximiuz/cdebug

How to debug distroless containers with kubectl and cdebug dev.to/chainguard/debugging-… Thanks to @iximiuz for the help here

🖥️ iximiuz/cdebug cdebug - a swiss army knife of container debugging. Troubleshoot #containers & pods lacking shell and/or debugging tools. Expose endpoints from the host system to containers & #Kubernetes networks. github.com/iximiuz/cdebug #DevLps