Skip to Content
Tutorials

DevOps

DevOps tutorials for people who want an app to run the same way on every machine, not only on the one it was written on. Learn what each command does before you trust it. A copied command runs just as happily when it is wrong.

0 likes
Pin a Base Image by Digest Level: Advanced

Look up a base image digest, pin it in the FROM line, check the build used it and plan how to update it. After this, your builds are repeatable without missing security fixes.

0 likes
Add a HEALTHCHECK That Actually Fails Level: Advanced

Break an app on purpose and compare three health checks, then put the one that works in the Dockerfile. After this, unhealthy means the app is broken, not the check.

0 likes
Cap CPU and Memory So One Container Can't Starve the Host Level: Advanced

Set CPU and memory limits, watch them work, change them on a running container and set them in Compose. After this, one busy container cannot take the whole machine.

0 likes
Apply and Verify Log Rotation on an Existing Compose Service Level: Advanced

Show why restart leaves old log settings in place, recreate one service with bounded logging, and verify retained messages without changing engine defaults.

0 likes
Log In to a Private Registry From CI Level: Advanced

Log in to a password-protected registry the way a CI job should, push an image, log out, and see the GitHub Actions version. After this, CI logins stop leaking tokens.

0 likes
Read-Only Root Filesystem With a Writable tmpfs Level: Advanced

Find where an app writes, run it read-only, and give it a tmpfs for scratch files and a volume for data. After this, nothing inside the container can change its own files.

0 likes
Zero-Downtime Restart With Compose on One Host Level: Advanced

Deploy a new version with blue and green copies, a proxy reload and a switch script, and prove no request failed. After this, a deployment on one host does not drop users.

0 likes
Export an SBOM or Scan Result From a Real Build Level: Advanced

Export an SPDX SBOM from a real build, list its packages and scan it with Grype, without a Docker account. After this, you can hand over what is in an image and what was known about it on a given day.