Challenge, Medium,  on  Containers

Restart a Container With Limited Resources

Premium Challenge

Upgrade your membership to unlock this and all other premium materials.

Upgrade

You've logged into an overloaded server where CPU and RAM usage are nearly maxed out. The culprit is a resource-intensive container. Your mission: identify and stop the offending container, then launch a new one with the same image and name. Ensure the new container's resource usage is capped between 50% and 60% of the server's CPU and RAM.

Good luck!

Hint 1

You can use docker ps to list all running containers and docker stop to stop a container by its name or ID.

Hint 2

Every container on the host (including stopped ones) should have a unique name. Make sure you removed the old container before starting a new one. You can use docker ps -a to list all containers, including stopped ones and docker rm to remove a container by its name or ID.

Hint 3

To limit the CPU usage of a container, you need to pass an extra flag (or two) to the docker run command. Try docker run --help and see what options are CPU-related.

Hint 4

Same as with CPU, you need to pass an extra flag (or two) to the docker run command. Try docker run --help and see what options are memory-related.

How to Author Challenges on iximiuz Labs

Instead of providing a subpar online editing experience, iximiuz Labs offers a helper CLI tool called labctl, allowing you to use your favorite text editor (or a full-featured IDE) to write content from the comfort of your local machine.

Install labctl CLI

curl -sf https://labs.iximiuz.com/cli/install.sh | sh

This will download and install the latest version of the labctl CLI. You only need to do this once per workstation.

Authorize labctl

labctl auth login

This will open a browser window asking you to authorize labctl to access your account. You need to do it after a fresh install of labctl and repeat it whenever the auth session expires.

Pull challenge content

labctl content pull challenge start-container-with-limited-resources

This will create a local copy of the challenge content in a directory named start-container-with-limited-resources. You only need to do this once per challenge.

Stream your changes

labctl content push -fw challenge start-container-with-limited-resources

Run this command in a separate terminal to continuously upload your changes to the server while editing the challenge in your favorite text editor or IDE.

You can also use labctl to create, list, and delete your content. Learn more about the available commands: labctl content --help

Start challenge