Inspect OCI Image Layout of Single- and Multi-Platform Images
Save container images as OCI layouts and explore the on-disk structure of single-platform (manifest-based) and multi-platform (index-based) images.
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.
Save container images as OCI layouts and explore the on-disk structure of single-platform (manifest-based) and multi-platform (index-based) images.
Practice optimizing applications' container images using multi-stage builds. Rewrite single-stage Dockerfiles for a Go backend and a TypeScript frontend to produce smaller, production-ready images without unnecessary build tools and dev dependencies.
Build a container image from a Dockerfile and use Docker commands to inspect its size and layer composition.
Practice building and compiling applications inside their Dockerfiles by containerizing a Go backend and a TypeScript frontend.
Learn how to configure a Docker host and its containers to automatically restart when the server reboots or the Docker daemon restarts.
Unlike Docker, Podman is daemonless and requires some extra systemd help to monitor and restart containers. Learn how to configure a Podman host and its containers to automatically restart after a server reboot.
Leverage your knowledge of Linux namespaces to reach an application's internal debug interface without installing anything into the container.
Learn how to run multiple Docker containers sharing the same PID, IPC, and network namespaces - a foundation of many advanced container use cases, including Kubernetes Pods construction and container debugging tools.
Explore the key container management operations by walking through all the phases of the container lifecycle - from creation to termination and removal.
Your Docker host has been in use for a while. Anonymous and named volumes piled up, disk space is tight, and it's time to clean stuff up.