{"id":36932,"date":"2026-01-23T19:08:16","date_gmt":"2026-01-23T13:38:16","guid":{"rendered":"https:\/\/codeforgeek.com\/?p=36932"},"modified":"2026-04-15T23:32:50","modified_gmt":"2026-04-15T18:02:50","slug":"docker-commands","status":"publish","type":"post","link":"https:\/\/codeforgeek.com\/docker-commands\/","title":{"rendered":"All Docker Commands Explained with Examples (2026 Complete Reference)"},"content":{"rendered":"\n

Docker is one of the most popular tools in 2026 for running applications inside containers. Learning Docker commands helps you create, start, manage, and troubleshoot containers with ease.<\/p>\n\n\n\n

Our goal is that instead of memorising these commands, you actually understand what each command does, why it exists, and when to use it in real projects<\/em><\/strong>. This way, you can start solo-leveling your Docker CLI skills with confidence.<\/p>\n\n\n\n

Essential Docker Commands for Container Lifecycle<\/h2>\n\n\n\n

We use these fundamental Docker commands to manage the entire life of a container. This includes creating, starting, and removing containers.<\/p>\n\n\n\n

docker run<\/h3>\n\n\n\n

This command creates and starts a new container from an image. It is the primary way to launch a container. We use it to run applications in an isolated environment. The result is a running container based on the specified image.<\/p>\n\n\n\n

Example:<\/strong><\/p>\n\n\n

\ndocker run -d -p 80:80 nginx\n<\/pre><\/div>\n\n\n
docker start<\/h3>\n\n\n\n
This command starts one or more stopped containers. It does not create a new container but restarts an existing one that is not running. We use this to resume work on a container we created earlier. The container enters the running state after execution.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker start my_container\n<\/pre><\/div>\n\n\n
docker stop<\/h3>\n\n\n\n
This command stops a running container gracefully. It sends a signal to the process to allow it to shut down properly. We use this to turn off containers without causing data corruption. The result is a container in a stopped state.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker stop my_container\n<\/pre><\/div>\n\n\n
docker restart<\/h3>\n\n\n\n
This command stops and then starts a container again. We use it when we need to apply configuration changes or fix minor glitches. It is a quick way to refresh a running service. The container is briefly down and then starts running again.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker restart my_container\n<\/pre><\/div>\n\n\n
docker pause<\/h3>\n\n\n\n
This command suspends all processes in a container. It freezes the container in its current state. We use this to temporarily free up system resources. The container remains on the disk but stops using CPU cycles.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker pause my_container\n<\/pre><\/div>\n\n\n
docker unpause<\/h3>\n\n\n\n
This command resumes all processes in a paused container. It unfreezes the container so it continues running from where it left off. We use this to restore services that we paused earlier. The container returns to an active running state.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker unpause my_container\n<\/pre><\/div>\n\n\n
docker rm<\/h3>\n\n\n\n
This command removes one or more containers. It deletes the container permanently from the system. We use this to clean up old containers we no longer need. The result is more free disk space and a cleaner system.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker rm my_container\n<\/pre><\/div>\n\n\n
docker kill<\/h3>\n\n\n\n
This command immediately stops a running container. It sends a signal that forces the process to quit instantly. We use this when a container is stuck or not responding to the stop command. The container shuts down immediately.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker kill my_container\n<\/pre><\/div>\n\n\n
Docker Commands for Image Management<\/h2>\n\n\n\n
We need a good set of Docker commands to handle images effectively. Images are the blueprints for our containers, so managing them is key.<\/p>\n\n\n\n
docker pull<\/h3>\n\n\n\n
This command downloads an image from a registry like Docker Hub. It saves the image to your local machine. We use this to get the latest version of an application before running it. The result is an image ready for use in containers.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker pull ubuntu:latest\n<\/pre><\/div>\n\n\n
docker build<\/h3>\n\n\n\n
This command builds an image from a Dockerfile. It reads the instructions in the file and creates a custom image. We use this to create our own application environments. The result is a new image that includes our specific code and settings.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker build -t myapp .\n<\/pre><\/div>\n\n\n
docker images<\/h3>\n\n\n\n
This command lists all images stored locally on your machine. It shows the repository, tags, and size of each image. We use this to see what we have available to run. The result is a table of all downloaded images.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker images\n<\/pre><\/div>\n\n\n
docker rmi<\/h3>\n\n\n\n
This command removes one or more images from your system. It deletes the image files to free up disk space. We use this to clean up outdated or unused images. The image is permanently removed from local storage.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker rmi ubuntu:old\n<\/pre><\/div>\n\n\n
docker tag<\/h3>\n\n\n\n
This command creates a new tag for an image. It is like adding a nickname or specific version label to an existing image. We use this to prepare an image for uploading to a registry. The result is the same image referenced by a new name.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker tag myapp myrepo\/myapp:v1\n<\/pre><\/div>\n\n\n
docker save<\/h3>\n\n\n\n
This command saves an image to a tar file. It creates a single file backup of an image. We use this to move images to computers that do not have internet access. The result is a portable archive file of the image.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker save -o myimage.tar myapp\n<\/pre><\/div>\n\n\n
docker load<\/h3>\n\n\n\n
This command loads an image from a tar file into your local Docker. It is the opposite of the save command. We use this to restore images from a backup or transfer them. The result is the image appearing in your local list.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker load -i myimage.tar\n<\/pre><\/div>\n\n\n
docker history<\/h3>\n\n\n\n
This command shows the history of an image. It displays the layers and commands used to build the image. We use this to debug how an image was created or find its size. The result is a list of past layers.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker history myapp\n<\/pre><\/div>\n\n\n
Docker Commands for Information and Inspection<\/h2>\n\n\n\n
We must be able to see what is happening inside our system. These Docker commands help us inspect the state of containers and the Docker engine.<\/p>\n\n\n\n
docker ps<\/h3>\n\n\n\n
This command lists running containers. It shows a summary of all active containers on the host. We use this to quickly see which applications are running. The result includes container IDs, names, and status.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker ps\n<\/pre><\/div>\n\n\n
docker ps -a<\/h3>\n\n\n\n
This command lists all containers, both running and stopped. It gives a complete view of every container created. We use this to find old containers we might have forgotten. The result includes the entire history of containers.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker ps -a\n<\/pre><\/div>\n\n\n
docker inspect<\/h3>\n\n\n\n
This command provides detailed low-level information on an object. It shows configuration data and status in JSON format. We use this to troubleshoot issues or find specific settings like IP addresses. The result is a large text output with every detail.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker inspect my_container\n<\/pre><\/div>\n\n\n
docker logs<\/h3>\n\n\n\n
This command shows the logs generated by a container. It displays the standard output and standard error streams. We use this to debug applications that are crashing or misbehaving. The result is a text log of what happened inside the container.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker logs my_container\n<\/pre><\/div>\n\n\n
docker top<\/h3>\n\n\n\n
This command displays the running processes inside a container. It is similar to the top command on Linux. We use this to see what the application is doing right now. The result is a list of active processes and their IDs.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker top my_container\n<\/pre><\/div>\n\n\n
docker stats<\/h3>\n\n\n\n
This command shows a live stream of resource usage statistics. It displays CPU, memory, and network usage for all containers. We use this to monitor performance and find heavy users. The result is a live updating table of metrics.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker stats\n<\/pre><\/div>\n\n\n
docker port<\/h3>\n\n\n\n
This command lists port mappings for a container. It shows which ports on the host map to ports inside the container. We use this to verify our networking configuration is correct. The result helps us access the application from the browser.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker port my_container\n<\/pre><\/div>\n\n\n
docker diff<\/h3>\n\n\n\n
This command inspects changes to files or directories in a container. It compares the current state to the original image. We use this to see which files were created or modified during runtime. The result is a list of changed files.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker diff my_container\n<\/pre><\/div>\n\n\n
docker events<\/h3>\n\n\n\n
This command shows real-time events from the Docker server. It displays information like container creation, starting, or stopping. We use this to monitor system activity live. The result is a continuous stream of system events.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker events\n<\/pre><\/div>\n\n\n
docker info<\/h3>\n\n\n\n
This command displays system-wide information. It shows the number of containers, images, and storage drivers. We use this to check the health and configuration of the Docker installation. The result is a summary of the entire Docker environment.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker info\n<\/pre><\/div>\n\n\n
docker version<\/h3>\n\n\n\n
This command shows the Docker version information. It lists the version of the client and the server. We use this to check for updates or verify compatibility. The result is the specific version numbers for each component.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker version\n<\/pre><\/div>\n\n\n
Docker Commands for System Cleanup<\/h2>\n\n\n\n
Keeping our system clean is important for performance. These Docker commands help us remove unused data and free up space.<\/p>\n\n\n\n
docker system prune<\/h3>\n\n\n\n
This command removes unused data. It deletes stopped containers, unused networks, and dangling images. We use this to perform a quick cleanup of the system. The result is a cleaner environment with more free disk space.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker system prune\n<\/pre><\/div>\n\n\n
docker system prune -a<\/h3>\n\n\n\n
This command removes unused data more aggressively. It also removes all unused images, not just dangling ones. We use this when we need a lot of disk space quickly. The result is a fresh start with only active images left.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker system prune -a\n<\/pre><\/div>\n\n\n
docker system df<\/h3>\n\n\n\n
This command shows the amount of disk space used by Docker. It breaks down usage by images, containers, and volumes. We use this to understand what is taking up space. The result is a detailed report on disk usage.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker system df\n<\/pre><\/div>\n\n\n
Docker Commands for Networking<\/h2>\n\n\n\n
Networking connects our containers to each other and the outside world. We use these Docker commands to manage networks effectively.<\/p>\n\n\n\n
docker network create<\/h3>\n\n\n\n
This command creates a new network. It allows containers to communicate with each other securely. We use this to isolate groups of containers. The result is a new network segment we can attach containers to.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker network create my_network\n<\/pre><\/div>\n\n\n
docker network ls<\/h3>\n\n\n\n
This command lists all networks on the Docker host. It shows the names and drivers of the networks. We use this to see what networks are available. The result is a list of all network configurations.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker network ls\n<\/pre><\/div>\n\n\n
docker network inspect<\/h3>\n\n\n\n
This command displays detailed information on a network. It shows which containers are connected to it and their IP addresses. We use this to troubleshoot connectivity issues between containers. The result is a JSON view of the network settings.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker network inspect my_network\n<\/pre><\/div>\n\n\n
docker network connect<\/h3>\n\n\n\n
This command connects a container to a network. It links a running container to an existing network. We use this to add a container to a specific communication group. The container can now talk to others on that network.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker network connect my_network my_container\n<\/pre><\/div>\n\n\n
docker network disconnect<\/h3>\n\n\n\n
This command disconnects a container from a network. It removes the link between the container and the network. We use this to isolate a container or move it to another network. The container loses access to that specific network.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker network disconnect my_network my_container\n<\/pre><\/div>\n\n\n
docker network rm<\/h3>\n\n\n\n
This command removes one or more networks. It deletes the network configuration completely. We use this to clean up networks we no longer need. The network disappears from the host system.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker network rm my_network\n<\/pre><\/div>\n\n\n
docker network prune<\/h3>\n\n\n\n
This command removes all unused networks. It deletes networks that are not connected to any containers. We use this to keep the networking stack tidy. The result is a list of deleted network IDs.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker network prune\n<\/pre><\/div>\n\n\n
Docker Commands for Volume Management<\/h2>\n\n\n\n
Volumes allow us to store data permanently outside the container. These Docker commands help us manage that data effectively.<\/p>\n\n\n\n
docker volume create<\/h3>\n\n\n\n
This command creates a new volume. It sets up a storage area that persists even if the container is deleted. We use this to store databases or important user data. The result is a volume ready to be attached to a container.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker volume create my_volume\n<\/pre><\/div>\n\n\n
docker volume ls<\/h3>\n\n\n\n
This command lists all volumes on the host. It shows the names and drivers of the volumes. We use this to see what data storage areas exist. The result is a list of all available volumes.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker volume ls\n<\/pre><\/div>\n\n\n
docker volume inspect<\/h3>\n\n\n\n
This command displays detailed information on a volume. It shows the mount point and other configuration details. We use this to find where the data is stored on the host. The result is a JSON output with volume specifics.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker volume inspect my_volume\n<\/pre><\/div>\n\n\n
docker volume rm<\/h3>\n\n\n\n
This command removes one or more volumes. It permanently deletes the volume and its data. We use this only when we are sure we do not need the data anymore. The result is the removal of the storage area.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker volume rm my_volume\n<\/pre><\/div>\n\n\n
docker volume prune<\/h3>\n\n\n\n
This command removes all unused volumes. It deletes volumes that are not connected to any containers. We use this to clean up orphaned data storage. The result is a significant amount of recovered disk space.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker volume prune\n<\/pre><\/div>\n\n\n
Docker Commands for Interaction and Execution<\/h2>\n\n\n\n
Sometimes we need to go inside a container to run commands. These Docker commands allow us to interact directly with the container.<\/p>\n\n\n\n
docker exec<\/h3>\n\n\n\n
This command runs a command inside a running container. It lets us execute programs in the container’s environment. We use this to open a shell or run scripts inside the container. The result is the output of the command we ran.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker exec -it my_container \/bin\/bash\n<\/pre><\/div>\n\n\n
docker attach<\/h3>\n\n\n\n
This command attaches your terminal to a running container. It lets you view the main process output and interact with it. We use this to see what the application is printing in real time. The result is a direct connection to the container.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker attach my_container\n<\/pre><\/div>\n\n\n
docker cp<\/h3>\n\n\n\n
This command copies files between a container and the local filesystem. It moves data in and out of a running container. We use this to backup files or inject configuration changes. The result is the file appearing in the destination.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker cp file.txt my_container:\/path\/to\/file.txt\n<\/pre><\/div>\n\n\n
docker export<\/h3>\n\n\n\n
This command exports a container’s filesystem as a tar archive. It saves the current state of the container files. We use this to create a snapshot of a container. The result is a tar file of the container contents.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker export my_container > backup.tar\n<\/pre><\/div>\n\n\n
docker import<\/h3>\n\n\n\n
This command imports the contents from a tarball to create a filesystem image. It is the reverse of the export command. We use this to restore a container snapshot as a new image. The result is a new image created from the tar file.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker import backup.tar my_restored_image\n<\/pre><\/div>\n\n\n
Docker Commands for Registry and Login<\/h2>\n\n\n\n
We use these Docker commands to interact with image registries. They help us share our images with the world.<\/p>\n\n\n\n
docker login<\/h3>\n\n\n\n
This command logs in to a Docker registry. It authenticates your user account so you can push and pull private images. We use this to access our private repositories. The result is a successful authentication session.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker login\n<\/pre><\/div>\n\n\n
docker logout<\/h3>\n\n\n\n
This command logs out from a Docker registry. It ends the current session and removes credentials. We use this to secure our account on a shared computer. The result is a logged-out state.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker logout\n<\/pre><\/div>\n\n\n
docker search<\/h3>\n\n\n\n
This command searches the Docker Hub for images. It looks for images that match your search term. We use this to find official or community images to use. The result is a list of matching images with descriptions.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker search python\n<\/pre><\/div>\n\n\n
docker push<\/h3>\n\n\n\n
This command pushes an image or a repository to a registry. It uploads your local image to a remote server. We use this to share our applications with others or deploy to cloud servers. The result is the image available on the registry.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker push myrepo\/myapp:v1\n<\/pre><\/div>\n\n\n
Docker Commands for Swarm Services<\/h2>\n\n\n\n
For orchestrating multiple containers, Docker provides Swarm mode. These Docker commands help us manage services across many nodes.<\/p>\n\n\n\n
docker swarm init<\/h3>\n\n\n\n
This command initializes a new swarm. It turns the current Docker engine into a swarm manager. We use this to start a cluster of Docker nodes. The result is a swarm ready to accept worker nodes.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker swarm init --advertise-addr192.168.1.1\n<\/pre><\/div>\n\n\n
docker service create<\/h3>\n\n\n\n
This command creates a new service. It runs a specified number of replica containers across the swarm. We use this to deploy scalable applications. The result is a distributed service managed by Docker.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker service create --name my_web --replicas 3 nginx\n<\/pre><\/div>\n\n\n
docker service ls<\/h3>\n\n\n\n
This command lists all services running in the swarm. It shows the name, replicas, and ports of each service. We use this to see what is deployed across the cluster. The result is a summary of active services.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker servicels ls\n<\/pre><\/div>\n\n\n
docker service ps<\/h3>\n\n\n\n
This command lists the tasks of a service. It shows which nodes are running the containers for that service. We use this to check the distribution and health of the service. The result is a list of individual tasks.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker serviceps ps my_web\n<\/pre><\/div>\n\n\n
docker service scale<\/h3>\n\n\n\n
This command scales one or more replicated services. It increases or decreases the number of running containers. We use this to handle more traffic or save resources. The result is the service running with the new number of replicas.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker service scale my_web=5\n<\/pre><\/div>\n\n\n
docker service rm<\/h3>\n\n\n\n
This command removes one or more services. It deletes all containers and tasks associated with the service. We use this to stop and remove an application from the swarm. The service is no longer active.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker servicerm rm my_web\n<\/pre><\/div>\n\n\n
docker stack deploy<\/h3>\n\n\n\n
This command deploys a new stack or update an existing stack. It uses a compose file to define multiple services. We use this to deploy complex applications with many parts at once. The result is a running stack of services.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker stack deploy -c docker-compose.yml my_stack\n<\/pre><\/div>\n\n\n
docker node ls<\/h3>\n\n\n\n
This command lists all nodes in the swarm. It shows the manager and worker nodes. We use this to see the health and availability of the cluster. The result is a list of all participating machines.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker node ls\n<\/pre><\/div>\n\n\n
Docker Commands for Docker Compose<\/h2>\n\n\n\n
Most modern 2026 projects rely on Docker Compose to run multi-container applications. We use these Docker commands to manage the entire application stack easily.<\/p>\n\n\n\n
docker compose up<\/h3>\n\n\n\n
This command creates and starts containers for a service. It reads the compose file to build and run the application stack. We use this to launch our entire project with one command. The result is a running group of connected containers.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker compose up -d\n<\/pre><\/div>\n\n\n
docker compose down<\/h3>\n\n\n\n
This command stops and removes containers, networks, and images created by up. It cleans up the environment completely. We use this to shut down the project and free up resources. The result is a clean system with no compose containers running.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker compose down\n<\/pre><\/div>\n\n\n
docker compose build<\/h3>\n\n\n\n
This command builds or rebuilds services for the project. It reads the compose file to create fresh images. We use this when we change our code or Dockerfile. The result is updated images ready for deployment.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker compose build\n<\/pre><\/div>\n\n\n
docker compose ps<\/h3>\n\n\n\n
This command lists containers for the current compose project. It shows the status of each service defined in the file. We use this to check if our services are running correctly. The result is a status list of the application stack.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker compose ps\n<\/pre><\/div>\n\n\n
docker compose logs<\/h3>\n\n\n\n
This command shows log output from services. It displays the standard output of all running containers in the project. We use this to debug issues across multiple services at once. The result is a combined stream of application logs.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker compose logs -f\n<\/pre><\/div>\n\n\n
docker compose exec<\/h3>\n\n\n\n
This command executes a command in a running service container. It opens an interactive shell or runs a script inside a service. We use this to perform maintenance or access the database. The result is direct access to the service environment.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker compose exec web bash\n<\/pre><\/div>\n\n\n
docker compose pull<\/h3>\n\n\n\n
This command pulls service images from a registry. It downloads the latest versions of images defined in the compose file. We use this to update our environment before starting services. The result is the newest images stored locally.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker compose pull\n<\/pre><\/div>\n\n\n
docker compose push<\/h3>\n\n\n\n
This command pushes service images to a registry. It uploads the built images to a remote server like Docker Hub. We use this to share our images with a team or a server. The result is the images available in the cloud.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker compose push\n<\/pre><\/div>\n\n\n
Docker Commands for Context and CLI Management<\/h2>\n\n\n\n
We use these Docker commands to manage different Docker environments. They help us switch between local machines and remote hosts easily.<\/p>\n\n\n\n
docker context ls<\/h3>\n\n\n\n
This command lists all available contexts. It shows the names and descriptions of Docker endpoints. We use this to see which environments we can connect to. The result is a list of contexts like default and my-cloud.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker context ls\n<\/pre><\/div>\n\n\n
docker context use<\/h3>\n\n\n\n
This command sets the default docker context. It switches the CLI target to a specific environment. We use this to change from a local Docker engine to a remote one. The result is all subsequent commands running on the new host.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker context use my-cloud\n<\/pre><\/div>\n\n\n
docker context create<\/h3>\n\n\n\n
This command creates a new docker context. It adds a new endpoint configuration to the CLI. We use this to set up a connection to a remote Docker daemon. The result is a new context option available for use.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker context create my-context --docker"host=tcp:\/\/my-server:2376"\n<\/pre><\/div>\n\n\n
docker context rm<\/h3>\n\n\n\n
This command removes one or more contexts. It deletes the configuration for a specific endpoint. We use this to clean up old or unused connection details. The result is the context disappearing from the list.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker context rm my-context\n<\/pre><\/div>\n\n\n
Docker Commands for Plugin Management<\/h2>\n\n\n\n
Plugins extend the capabilities of Docker. We use these Docker commands to manage these extra extensions for special tasks.<\/p>\n\n\n\n
docker plugin ls<\/h3>\n\n\n\n
This command lists all installed plugins. It shows the names, versions, and status of plugins. We use this to see what extra capabilities are available. The result is a table of loaded plugins.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker plugin ls\n<\/pre><\/div>\n\n\n
docker plugin install<\/h3>\n\n\n\n
This command installs a plugin from a registry. It downloads and sets up the plugin extension. We use this to add specific features like storage drivers. The result is the plugin ready for use by Docker.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker plugin install vieux\/sshfs\n<\/pre><\/div>\n\n\n
docker plugin enable<\/h3>\n\n\n\n
This command enables a plugin. It activates a plugin that is currently disabled. We use this to start using the features of a specific plugin. The result is the plugin becoming active.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker plugin enable vieux\/sshfs\n<\/pre><\/div>\n\n\n
docker plugin disable<\/h3>\n\n\n\n
This command disables a plugin. It turns off the plugin so it is not used. We use this to troubleshoot issues or temporarily stop a feature. The result is the plugin becoming inactive.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker plugin disable vieux\/sshfs\n<\/pre><\/div>\n\n\n
docker plugin rm<\/h3>\n\n\n\n
This command removes one or more plugins. It deletes the plugin from the system. We use this when we no longer need the extension. The result is the plugin completely uninstalled.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker plugin rm vieux\/sshfs\n<\/pre><\/div>\n\n\n
Docker Commands for Buildx and Modern Builds<\/h2>\n\n\n\n
Modern applications often require images for different computer chips. We use these Docker commands to handle advanced building needs like multi-platform support.<\/p>\n\n\n\n
docker buildx ls<\/h3>\n\n\n\n
This command lists the available builder instances. It shows the current and available build drivers. We use this to check the status of our build environments. The result is a list of builder setups.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker buildx ls\n<\/pre><\/div>\n\n\n
docker buildx create<\/h3>\n\n\n\n
This command creates a new builder instance. It sets up a new environment for building images. We use this to configure a builder for multi-architecture builds. The result is a new builder ready for work.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker buildx create --name mybuilder\n<\/pre><\/div>\n\n\n
docker buildx build<\/h3>\n\n\n\n
This command starts a build using Buildx. It can build images for multiple platforms at the same time. We use this to create images for both Intel and ARM chips. The result is a multi-architecture image or set of images.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker buildx build --platform linux\/amd64,linux\/arm64 -t myapp:latest .\n<\/pre><\/div>\n\n\n
docker buildx inspect<\/h3>\n\n\n\n
This command inspects the current builder. It shows detailed configuration and status of the builder instance. We use this to verify the node status and platform capabilities. The result is detailed information about the builder.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker buildx inspect mybuilder\n<\/pre><\/div>\n\n\n
Docker Commands for Manifests<\/h2>\n\n\n\n
Manifests allow us to manage image manifests and lists. We use these pro-level Docker commands to handle multi-platform images manually.<\/p>\n\n\n\n
docker manifest create<\/h3>\n\n\n\n
This command creates a manifest list for local images. It groups images for different architectures under one tag. We use this to prepare a multi-platform image for distribution. The result is a manifest list pointing to specific images.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker manifest create myapp:latest myapp:amd64 myapp:arm64\n<\/pre><\/div>\n\n\n
docker manifest inspect<\/h3>\n\n\n\n
This command displays detailed information on a manifest list or image. It shows the configuration and supported platforms. We use this to verify the contents of a manifest. The result is a JSON view of the manifest data.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker manifest inspect myapp:latest\n<\/pre><\/div>\n\n\n
docker manifest push<\/h3>\n\n\n\n
This command pushes a manifest list to a repository. It uploads the multi-platform configuration to a registry. We use this to publish a single tag that supports multiple architectures. The result is users pulling the correct image automatically.<\/p>\n\n\n\n
Example:<\/strong><\/p>\n\n\n
\ndocker manifest push myapp:latest\n<\/pre><\/div>\n\n\n
Conclusion<\/h2>\n\n\n\n
We have covered a massive list of Docker commands in this guide. These tools give us the power to build, ship, and run any application anywhere. Keep practising these Docker commands and use this guide whenever you need a quick reference. You now have the knowledge to manage your Docker environment like a true professional.<\/p>\n\n\n\n
To further improve your Docker skills, check out this step-by-step guide:
Dockerize NodeJS Application<\/a><\/p>\n\n\n\n
Reference:
https:\/\/docs.docker.com\/engine\/reference\/commandline\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Docker is one of the most popular tools in 2026 for running applications inside containers. Learning Docker commands helps you create, start, manage, and troubleshoot containers with ease. Our goal is that instead of memorising these commands, you actually understand what each command does, why it exists, and when to use it in real projects. […]<\/p>\n","protected":false},"author":79,"featured_media":36945,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_surecart_dashboard_logo_width":"180px","_surecart_dashboard_show_logo":true,"_surecart_dashboard_navigation_orders":true,"_surecart_dashboard_navigation_invoices":true,"_surecart_dashboard_navigation_subscriptions":true,"_surecart_dashboard_navigation_downloads":true,"_surecart_dashboard_navigation_billing":true,"_surecart_dashboard_navigation_account":true,"_uag_custom_page_level_css":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-36932","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorial"],"blocksy_meta":[],"uagb_featured_image_src":{"full":["https:\/\/codeforgeek.com\/wp-content\/uploads\/2026\/01\/All-docker-commands.png",1920,1080,false],"thumbnail":["https:\/\/codeforgeek.com\/wp-content\/uploads\/2026\/01\/All-docker-commands-150x150.png",150,150,true],"medium":["https:\/\/codeforgeek.com\/wp-content\/uploads\/2026\/01\/All-docker-commands-300x169.png",300,169,true],"medium_large":["https:\/\/codeforgeek.com\/wp-content\/uploads\/2026\/01\/All-docker-commands-768x432.png",768,432,true],"large":["https:\/\/codeforgeek.com\/wp-content\/uploads\/2026\/01\/All-docker-commands-1024x576.png",1024,576,true],"1536x1536":["https:\/\/codeforgeek.com\/wp-content\/uploads\/2026\/01\/All-docker-commands-1536x864.png",1536,864,true],"2048x2048":["https:\/\/codeforgeek.com\/wp-content\/uploads\/2026\/01\/All-docker-commands.png",1920,1080,false]},"uagb_author_info":{"display_name":"Aditya Gupta","author_link":"https:\/\/codeforgeek.com\/author\/aditya\/"},"uagb_comment_info":0,"uagb_excerpt":"Docker is one of the most popular tools in 2026 for running applications inside containers. Learning Docker commands helps you create, start, manage, and troubleshoot containers with ease. Our goal is that instead of memorising these commands, you actually understand what each command does, why it exists, and when to use it in real projects.…","_links":{"self":[{"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/posts\/36932","targetHints":{"allow":["GET","POST","PUT","PATCH","DELETE"]}}],"collection":[{"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/users\/79"}],"replies":[{"embeddable":true,"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/comments?post=36932"}],"version-history":[{"count":1,"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/posts\/36932\/revisions"}],"predecessor-version":[{"id":37548,"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/posts\/36932\/revisions\/37548"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/media\/36945"}],"wp:attachment":[{"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/media?parent=36932"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/categories?post=36932"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/codeforgeek.com\/wp-json\/wp\/v2\/tags?post=36932"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}