![\"\"](\"http:\/\/bitcows.com\/wp-content\/uploads\/2019\/05\/docker5-1140x456.jpg\")
<\/p>\n<\/p>\n
In this article we\u2019ll look at 5 Docker CLI commands you should know. These might not be the most common commands but knowing about these will come in handy for debugging, free up memory and clean up. <\/p>\n
Stopping a container is pretty straight forward As seen above we use the same Lastly as seen above we can remove all images running or other wise by applying the same logic as before. Listing each image id and force removing them.<\/p>\n Lets say you have an image and you need to examine a log file in it, or add a file and re-tag it. You can use this command to bash or commandline into it and do your worst. First you will start up your image, and when its running you find out the containers ID by typing If you have limited resources on your server like I sometimes do. You might need to free up some memory. Doing a prune is the way to delete unused images that are just out there dangling and taking up valuable space. If you wan to remove all unused images not just dangling ones use the option Tag creates a tag from TARGET_IMAGE that refers to SOURCE_IMAGE. A good reason to do this is if you have an image that you don’t or can’t rebuild and you need to add or remove something to it. This way you can use the source image, edit and re-tag it as something new.<\/p>\n Obviously there are many more commands you can use and learn for Docker. These are just 5 that I have used consistanly over and over. Note: there are other options that can be combined with these commands if you need a list of them all check this out<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" In this article we\u2019ll look at 5 Docker CLI commands you should know. These might not be the most common commands but knowing about these will come in handy for debugging, free up memory and clean up. 1. Stopping All Containers Stopping a container is pretty straight forward docker stop my_container but what if you…<\/p>\ndocker stop my_container<\/code> but what if you wanted to stop them all? Here you see we we can loop all the containers an print out the ID’s of each one. docker ps<\/code> lists the containers -a<\/code> causes all the container to be listed regardless if they are running or not, -q<\/code> only display numeric IDs. <\/p>\ndocker stop $(docker ps -a -q)<\/pre>\n
2. Cleanup and Remove Containers and Images<\/h2>\n
$(docker ps -a -q)<\/code> to list all the containers. Then we use docker rm<\/code> to remove them and -f<\/code> forces the removal of a running container.<\/p>\ndocker rm -f $(docker ps -a -q)<\/pre>\n
docker rmi -f $(docker images -q)<\/pre>\n
3.Bash<\/h2>\n
docker ps<\/code> then take that container’s ID and insert it in the below command. You should then see a command prompt that puts you inside the running container.<\/p>\ndocker exec -it [CONTAINER_ID] bash<\/pre>\n
4.Prune<\/h2>\n
-a<\/code>. This also works for containers, this removes all stopped containers but unlike the command above it won’t remove ALL containers.<\/p>\ndocker image prune<\/pre>\n
docker container prune<\/pre>\n
5. Tag<\/h2>\n
docker tag SOURCE_IMAGE[:TAG] TARGET_IMAGE[:TAG]<\/pre>\n
docker image tag my_old_image:1.0 my_new_image:1.1<\/pre>\n
Conclusion<\/h2>\n