Pausing a container temporarily suspends its processes without stopping or killing the workload. It's useful during peak load hours for reducing the impact of the non-critical workloads, maintenance windows, or when you want to "stop the world" to investigate a security incident or troubleshoot a bug.
In this challenge, you'll launch a resource-hungry app, then pause it, explore the state of the container, and finally unpause it back to life. Good luck!
Launch the target container using the following image:
ghcr.io/iximiuz/labs/resource-hog/herder:v1.0.0
Pause the container so its processes are suspended, but the container remains running:
Hint: Pausing vs stopping 💡
When you stop a container, all container's processes get terminated, but its filesystem and metadata remain intact, so you can restart it again later.
When you pause a container, all container's processes get suspended, but you can still find them in the host's process list, and the container is technically considered to be still running.
Inspect the container's state and identify its status:
Hint: Inspecting container state 💡
If you need a refresher on how to inspect the container state, solve this challenge first.
Finally, unpause the container so its process(es) are resumed:
Level up your Server Side game — Join 13,000 engineers who receive insightful learning materials straight to their inbox