Menu
What artifacts do stopped docker containers leave on the host file system that makes it necessary to run the command "docker container prune". I thought docker containers where simply running versions of images that are suppose to be wiped out after they exit? In what scenarios are artifacts left behind if it is not always the case?
773
Remove a container and its volumes This command removes the container and any volumes associated with it. Note that if a volume was specified with a name, it will not be removed.
Its always better to stop the container and then remove it using the remove command. Stopping the container and then removing it will allow sending SIG_HUP signal to recipients. This will ensure that all the containers have enough time to clean up their tasks.
The container has consumed too much memory, and has been killed by the host OS: If the operating system detects that it's running out of memory, it might start killing processes to free up memory. If a container is using a lot of memory or resources, it might be killed by the OS.
If you don't use --rm to auto-remove the container when it exits then the container is only stopped, not removed. It can be resumed with docker start. You can run new commands inside it with docker exec. All of the files that were modified during the container's runtime are still there: log files, data files, anything that was modified, added, or removed. Docker also keeps around metadata like the container's logs and its exit status in case you want to do a post mortem inspection.
It should be standard practice to use --rm so containers clean up after themselves. Otherwise you'll have to periodically clean up your system.
189
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
