Stopping, Removing Containers, and Naming Containers

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3074745e412c docker-rust-image "/bin/server" 6 minutes ago Up 4 seconds 0.0.0.0:3001->8000/tcp wonderful_kalam 6cfa26e2e3c9 docker-rust-image "/bin/server" 16 minutes ago Exited (0) 7 minutes ago friendly_montalcini 4cbe94b2ea0e docker-rust-image "/bin/server" 18 minutes ago Exited (0) 17 minutes ago tender_bose ``` Notice that the container you just restarted has been started in detached mode. Also, observe the status of the container is "Up X seconds". When you restart a container, it starts with the same flags or commands that it was originally started with. Now, stop and remove all of your containers and take a look at fixing the random naming issue. Stop the container you just started. Find the name of your running container and replace the name in the following command with the name of the container on your system. ```console $ docker stop wonderful_kalam wonderful_kalam ``` Now that you have stopped all of your containers, remove them. When you remove a container, it's no longer running, nor is it in the stopped status, but the process inside the container has been stopped and the metadata for the container has been removed. To remove a container, run the `docker rm` command with the container name. You can pass multiple container names to the command using a single command. Again, replace the container names in the following command with the container names from your system. ```console $ docker rm wonderful_kalam friendly_montalcini tender_bose wonderful_kalam friendly_montalcini tender_bose ``` Run the `docker ps --all` command again to see that Docker removed all containers. Now, it's time to address the random naming issue. Standard practice is to name your containers for the simple reason that it's easier to identify what's running in the container and what application or service it's associated with. To name a container, you just need to pass the `--name` flag to the `docker run` command. ```console $ docker run -d -p 3001:8000 --name docker-rust-container docker-rust-image 1aa5d46418a68705c81782a58456a4ccdb56a309cb5e6bd399478d01eaa5cdda $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c68fa18de1f6 docker-rust-image "/bin/server" 7 seconds ago Up 6 seconds 0.0.0.0:3001->8000/tcp docker-rust-container ``` That’s better! You can now easily identify your container based on the name. ## Summary In this section, you took a look at running containers. You also took a look at managing containers by starting, stopping, and restarting them. And finally, you looked at naming your containers so they are more easily identifiable. Related information: - [docker run CLI reference](/reference/cli/docker/container/run.md) ## Next steps In the next section, you’ll learn how to run a database in a container and connect it to a Rust application.

This section guides you through stopping and removing Docker containers using `docker stop` and `docker rm`. It emphasizes the importance of naming containers for easy identification using the `--name` flag during the `docker run` command. The section concludes with a summary of container management tasks and points to the next steps, which involve running a database in a container and connecting it to a Rust application.