Reach a Distroless Container's Debug Endpoint From a Sidecar Container
A distroless container serves a debug interface on its own loopback address. Can you reach this debug endpoint using nothing but standard Docker commands?
Focused, hands-on problems for sharpening your DevOps and server-side skills. Some teach specific concepts while others mirror real-world scenarios. Every challenge includes hints, feedback, and automated solution checks.
A distroless container serves a debug interface on its own loopback address. Can you reach this debug endpoint using nothing but standard Docker commands?
You are containerizing the dev workflows of a legacy Python service and you need to find out which external services its test suite talks to. Can you think of an easy way to do it?
Ad-hoc containers are a handy way to run command-line tools without installing them on the host. Use one to access a production Redis server and turn off a feature flag. But beware of the gotcha: the production server can only be tunneled to the localhost.
Can you get several builds of an app running side by side without port conflicts, so you can test them simultaneously?
Prove your Linux networking skills by connecting two network namespaces with a virtual Ethernet device.
There is a container that can reach the host only through its veth pair and cannot call any other addresses. Can you connect it to the outside world?