{"id":14085,"date":"2022-10-03T14:20:26","date_gmt":"2022-10-03T14:20:26","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=14085"},"modified":"2025-07-12T05:40:16","modified_gmt":"2025-07-12T05:40:16","slug":"docker-update-command-explained-with-examples","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/docker-update-command-explained-with-examples\/","title":{"rendered":"Docker Tutorials: docker update command explained with examples"},"content":{"rendered":"\n

The docker update<\/strong> command dynamically updates container configuration<\/strong>. You can use this command to prevent containers from consuming too many resources such as CPU and memory from their Docker host. With a single command, you can place limits on a single container or on many.<\/p>\n\n\n\n

Notes<\/strong><\/p>\n\n\n\n

With the exception of the –kernel-memory option, you can specify these options on a running or a stopped container. On kernel version older than 4.6, you can only update –kernel-memory on a stopped container or on a running container with kernel memory initialized.<\/p>\n\n\n\n

The docker update command dynamically updates container configuration. You can use this command to prevent containers from consuming too many resources such as CPU and memory from their Docker host. With a single command, you can place limits on a single container or on many.<\/p>\n\n\n\n

Notes<\/strong><\/p>\n\n\n\n

With the exception of the –kernel-memory option, you can specify these options on a running or a stopped container. On kernel version older than 4.6, you can only update –kernel-memory on a stopped container or on a running container with kernel memory initialized.<\/p>\n\n\n\n

You can use “docker container update” instead of “docker update” as well.<\/strong><\/p>\n\n\n\n

Docker update command Example<\/strong><\/p>\n\n\n\n