Build and Push an Uncompressed Container Image
Learn how to build and publish an uncompressed container image - a helpful trick to optimize disk I/O for large images, especially when you can benefit from a fast internal network.
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.
Learn how to build and publish an uncompressed container image - a helpful trick to optimize disk I/O for large images, especially when you can benefit from a fast internal network.
Learn how to build a secure, lightweight, and production-ready container image for a statically linked Go application by following this hands-on challenge full of practical tips and tricks.
Learn how to build a secure, lightweight, and production-ready Node.js container image for a SvelteKit application by following this hands-on challenge full of practical tips and tricks.
Learn how to build a secure, lightweight, and production-ready Node.js container image for a Nuxt application by following this hands-on challenge full of practical tips and tricks.
Can you make a container exit gracefully after the 'docker stop' command while preserving its extensible entrypoint mechanism?
Learn how to build a secure, lightweight, and production-ready Node.js container image for a Next.js application by following this hands-on challenge full of practical tips and tricks.
Learn how to copy a multi-platform image from one repository to another using the docker manifest command or other, more convenient, tools like crane, skopeo, or regctl.
Learn how to fine-tune the container's cgroup to make the container exit when one of its processes runs out of memory.
Run a multi-container Docker Compose application limiting its total CPU and memory usage without specifying the individual container's limits.
Prove your SRE skills - identify and stop an overloaded container, then start a new one with limited CPU and RAM resources.