Focused hands-on problems designed to help you hone your DevOps or Server Side skills. Some challenges are more educational, while others are based on real-world scenarios. The platform provides hints and feedback for each challenge, including automated solution checks.
Challenges crafted by iximiuz Labs to help you master DevOps and Server Side topics.
Practice pausing and resuming a running container: start a resource-hungry container, pause it, inspect its state, and then unpause it back to life.
Practice pausing (freeze) and resuming (thaw) a resource-hungry Linux process using the cgroup v2 freezer mechanism.
Practice using UNIX signals with containers for controlling application behavior: Send a SIGUSR1 to a containerized app to trigger its memory usage reporting.
Learn how to configure the restart policy for a container so that it restarts automatically on application failure.
Challenges from outstanding independent authors proudly hosted by iximiuz Labs.
In this challenge, you’ll debug and fix a deliberately “broken” eBPF program, then prove it’s running by identifying its program and map IDs. Along the way, you’ll explore bpftool, check which helpers are supported, and dig into details like the UID of the loader. Finally, you’ll test your knowledge of eBPF maps by recalling the flag that only inserts a key if it doesn’t already exist.
Get hands-on with reading secrets from different providers and using them in your Dagger pipelines.
Learn how to install, update and uninstall Dagger module dependencies.
Challenges contributed by the community members sharing their knowledge and expertise.
Configure a Kubernetes Deployment to consume Secrets as environment variables and volume mounts.
Master **sed**, the essential stream editor for Linux SysAdmins. Progress through 10 tasks: simple & global substitution, regex patterns, line ranges, deletion, insertion, ... Work with realistic Rocky Linux system files in /home/laborant/sed_challenge/.
Practice the fundamental lifecycle of a Kubernetes Pod: creation, inspection (IP, node), interaction (executing commands, checking logs), and deletion.
This exercise tests your ability to safely upgrade a multi-node Kubernetes cluster from version 1.30 to 1.31 following the standard upgrade procedure.
