Verify Downloaded Files with SHA-256 Checksums
Practice using SHA-256 checksums to verify file integrity, detect corrupted or modified files, and confirm that downloaded data matches the original.
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
Challenges crafted by iximiuz Labs to help you master DevOps and Server Side topics.
Practice using SHA-256 checksums to verify file integrity, detect corrupted or modified files, and confirm that downloaded data matches the original.
Practice authenticating to an HTTP API from the command line using both a username and password and a bearer token, and learn a couple of tricks along the way.
Learn how to access a service bound to localhost of the Docker host from a bridge-networked container, without exposing the service to the local network or disabling network isolation.
An internal service started receiving requests from unexpected IP addresses. Identify the unexpected sources and find out which workloads and teams are behind them.
Challenges from outstanding independent authors proudly hosted by iximiuz Labs.
Did you know that pods can become invisible? Can you figure out how?
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.
Challenges contributed by the community members sharing their knowledge and expertise.
A stock Django + Strawberry GraphQL service ships with five common weaknesses. Probe each one from the terminal, fix it in the real project, and watch the lab confirm the remediation against the live endpoint.
node-01 is due for maintenance, and it hosts two of the three checkout-api replicas. Add a PodDisruptionBudget so the drain can never take checkout below two available replicas, then drain the node.
A worker node dropped to NotReady and part of the workload went with it. The container runtime is fine and the control plane is healthy; the trail leads from kubectl symptoms down into systemd and the kubelet configuration. Diagnose the node and bring it back.
Build five ways to combine containers in one Pod: a sidecar that extends the app, an init container that finishes before the app starts, a native sidecar with a startup guarantee, an ambassador that mutates an outbound call, and an adapter that translates an inbound one.