From 15b0e335424d6a04de822af58a81886d7e94ac47 Mon Sep 17 00:00:00 2001 From: Anthony Pun Date: Sun, 2 Jun 2024 11:53:45 -0700 Subject: [PATCH] Fix: Standardize using "docker container ls" command when referencing listing containers (#5787) --- .../roadmaps/docker/content/108-running-containers/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/data/roadmaps/docker/content/108-running-containers/index.md b/src/data/roadmaps/docker/content/108-running-containers/index.md index 2ff1e4dd5..2472cb972 100644 --- a/src/data/roadmaps/docker/content/108-running-containers/index.md +++ b/src/data/roadmaps/docker/content/108-running-containers/index.md @@ -16,7 +16,7 @@ This starts a new container and maps the host's port 8080 to the container's por ## Listing Containers -To list all running containers, use the `docker ps` command. To view all containers (including those that have stopped), use the `-a` flag: +To list all running containers, use the `docker container ls` command. To view all containers (including those that have stopped), use the `-a` flag: ```bash docker container ls -a @@ -30,7 +30,7 @@ To access a running container's shell, use the `docker exec` command: docker exec -it CONTAINER_ID bash ``` -Replace `CONTAINER_ID` with the ID or name of your desired container. You can find this in the output of `docker ps`. +Replace `CONTAINER_ID` with the ID or name of your desired container. You can find this in the output of `docker container ls`. ## Stopping Containers