Docker has revolutionized the way we build, ship, and run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> applications by enabling developers to package their applications and dependencies into containers. This containerization technology comes with a multitude of features, among which the ability to set resource limits is crucial for ensuring that your applications run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> efficiently and do not consume excessive system resources. In this article, we will delve into how to manage resource limits in Docker containers, explore the various options available, and understand the implications of these settings.<\/p>\n Antes de adentrarse en los detalles de c\u00f3mo establecer l\u00edmites de recursos, es esencial comprender lo que implica la gesti\u00f3n de recursos en Docker. La gesti\u00f3n de recursos permite especificar cu\u00e1nta CPU, memoria y E\/S (I\/O) puede utilizar un contenedor de Docker. contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can consume. By imposing limits, you can prevent a single contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> from monopolizing system resources, thus ensuring that other containers and the host system remain performant and stable.<\/p>\n Docker utiliza tanto l\u00edmites duros como suaves para la gesti\u00f3n de recursos:<\/p>\n L\u00edmites absolutos<\/strong>: These limits are strict and cannot be exceeded under any circumstances. For example, if you set a memory limit, the contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> will be terminated if it attempts to exceed that limit.<\/p>\n<\/li>\n Soft Limits<\/strong>: These limits allow some leeway. For instance, with CPU shares, a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can use more CPU resources when available, but it will be throttled when competing with other containers for CPU time.<\/p>\n<\/li>\n<\/ul>\n Docker ofrece varias opciones para controlar la asignaci\u00f3n de recursos de CPU, incluyendo:\n\n- **CPU Shares**: Permite establecer una proporci\u00f3n relativa de CPU que se asignar\u00e1 a un contenedor en comparaci\u00f3n con otros contenedores. Por ejemplo, si un contenedor tiene 1024 shares y otro tiene 512, el primero recibir\u00e1 el doble de tiempo de CPU que el segundo.\n\n- **CPU Period**: Define el per\u00edodo de tiempo (en microsegundos) para el cual se mide el uso de CPU. El valor predeterminado es 100000 (100ms).\n\n- **CPU Quota**: Especifica la cantidad m\u00e1xima de tiempo de CPU (en microsegundos) que un contenedor puede usar durante cada per\u00edodo de CPU. Por ejemplo, si el per\u00edodo es 100000 y la cuota es 50000, el contenedor puede usar hasta el 50% de un n\u00facleo de CPU.\n\n- **CPU Set**: Permite restringir un contenedor a un conjunto espec\u00edfico de n\u00facleos de CPU. Por ejemplo, puedes asignar un contenedor para que solo use los n\u00facleos 0 y 1.\n\n- **CPU Affinity**: Similar al CPU Set, pero permite una mayor flexibilidad al especificar qu\u00e9 n\u00facleos de CPU puede usar un contenedor.\n\n- **CPU CFS (Completely Fair Scheduler)**: Es el programador de CPU predeterminado en Linux. Docker utiliza CFS para gestionar la asignaci\u00f3n de CPU entre contenedores.\n\n- **CPU Limit**: Establece un l\u00edmite m\u00e1ximo en el uso de CPU para un contenedor. Por ejemplo, puedes limitar un contenedor para que no use m\u00e1s del 80% de un n\u00facleo de CPU.\n\n- **CPU Reservation**: Garantiza que un contenedor recibir\u00e1 una cantidad m\u00ednima de tiempo de CPU, incluso si otros contenedores est\u00e1n usando la mayor\u00eda de los recursos.\n\n- **CPU Priority**: Permite establecer una prioridad para un contenedor, lo que influye en la cantidad de tiempo de CPU que recibe en comparaci\u00f3n con otros contenedores.\n\n- **CPU Burst**: Permite que un contenedor use m\u00e1s CPU de la que se le ha asignado durante un corto per\u00edodo de tiempo, si los recursos est\u00e1n disponibles.\n\nEstas opciones se pueden combinar para crear configuraciones de CPU personalizadas que se adapten a las necesidades espec\u00edficas de tus aplicaciones y cargas de trabajo. El You can specify fractional values as well. If you set it to El Ejemplo:<\/p>\n In this case, the contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> will receive CPU time based on the weight you have assigned relative to others.<\/p>\n El Ejemplo:<\/p>\n In this case, the contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can only run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> on CPU cores 0 and 1.<\/p>\n Memory limits can be set using the El Ejemplo:<\/p>\n This command restricts the contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> to use a maximum of 512 MB of RAM.<\/p>\n El Ejemplo:<\/p>\n En este escenario, Understanding Docker Resource Management<\/h3>\n
\n
Setting Resource Limits for CPU<\/h3>\n
--cpus<\/code>, --cpu-shares<\/code>, and --cpus del conjunto de cpus<\/code>.<\/p>\n1. Usando
--cpus<\/code><\/h4>\n--cpus<\/code> flag allows you to limit the total number of CPUs that a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can use. For instance, if you want to restrict a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> to use only 2 CPUs, you can run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>:<\/p>\ndocker run --cpus=\"2.0\" mi_app<\/code><\/pre>\n0.5<\/code>, the contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> will be allowed to use half of one CPU core.<\/p>\n2. Using
--cpu-shares<\/code><\/h4>\n--cpu-shares<\/code> option is a way to specify the relative weight of CPU allocation for a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span>. By default, Docker sets the CPU share to 1024. If you run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> con --cpu-shares=512<\/code>, it will receive half the CPU time compared to containers with the default share under heavy load.<\/p>\nDocker es una plataforma de c\u00f3digo abierto que permite automatizar el despliegue de aplicaciones dentro de contenedores de software. Proporciona una capa adicional de abstracci\u00f3n y automatizaci\u00f3n de virtualizaci\u00f3n a nivel de sistema operativo en Linux.\n\nLos contenedores Docker empaquetan una aplicaci\u00f3n con todas sus dependencias en un formato estandarizado que puede ejecutarse en cualquier entorno Linux. Esto facilita enormemente el desarrollo, el testing y el despliegue de aplicaciones, ya que se eliminan los problemas de \"funciona en mi m\u00e1quina\".\n\nAlgunas de las caracter\u00edsticas clave de Docker son:\n\n- Aislamiento: Cada contenedor se ejecuta de forma aislada, con su propio sistema de archivos, procesos, etc.\n\n- Portabilidad: Los contenedores pueden ejecutarse en cualquier entorno Linux sin necesidad de modificarlos.\n\n- Ligereza: Los contenedores comparten el kernel del sistema operativo anfitri\u00f3n, lo que los hace mucho m\u00e1s ligeros que las m\u00e1quinas virtuales tradicionales.\n\n- Escalabilidad: Es muy f\u00e1cil escalar horizontalmente una aplicaci\u00f3n ejecutando m\u00faltiples instancias de un contenedor.\n\nDocker se ha convertido en una herramienta fundamental en el desarrollo de aplicaciones modernas, especialmente en el contexto de la arquitectura de microservicios y la computaci\u00f3n en la nube. run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> --cpu-shares=512 my_app<\/code><\/pre>\n3. Usando
--cpus del conjunto de cpus<\/code><\/h4>\n--cpus del conjunto de cpus<\/code> option allows you to specify which logical CPUs (cores) a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> lata run<\/a><\/span>\"RUN\" refers to a command in various programming languages and operating systems to execute a specified program or script. It initiates processes, providing a controlled environment for task execution. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> on. This is especially useful for multi-core systems where you may want to restrict a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> to a specific set of CPUs.<\/p>\ndocker run --cpuset-cpus=\"0,1\" mi_app<\/code><\/pre>\nEstablecer l\u00edmites de recursos para la memoria\n\nEn este cap\u00edtulo, aprender\u00e1 a establecer l\u00edmites de recursos para la memoria. Los l\u00edmites de recursos para la memoria se establecen de la misma manera que los l\u00edmites de recursos para la CPU. Para establecer l\u00edmites de recursos para la memoria, utilice la opci\u00f3n --memory. Por ejemplo, para establecer un l\u00edmite de memoria de 128 MB para un contenedor, ejecute el siguiente comando:\n\n```\n# docker run -d --name ch5_mariadb --memory 128m \\\n-v \/var\/ch5_mariadb:\/var\/lib\/mysql \\\n-e MYSQL_ROOT_PASSWORD=mypass \\\n-e MYSQL_DATABASE=my_data \\\n-e MYSQL_USER=vsftpd \\\n-e MYSQL_PASSWORD=mypass \\\nmariadb:latest\n```\n\nEn este ejemplo, el l\u00edmite de memoria se establece en 128 MB. El contenedor no podr\u00e1 utilizar m\u00e1s de 128 MB de memoria. Si el contenedor intenta utilizar m\u00e1s de 128 MB de memoria, se detendr\u00e1.\n\nTambi\u00e9n puede establecer un l\u00edmite de memoria suave utilizando la opci\u00f3n --memory-reservation. Un l\u00edmite de memoria suave es un l\u00edmite que el contenedor puede superar temporalmente. Sin embargo, si el contenedor supera el l\u00edmite de memoria suave durante un per\u00edodo prolongado de tiempo, se detendr\u00e1.\n\nPor ejemplo, para establecer un l\u00edmite de memoria suave de 64 MB para un contenedor, ejecute el siguiente comando:\n\n```\n# docker run -d --name ch5_mariadb --memory 128m \\\n--memory-reservation 64m \\\n-v \/var\/ch5_mariadb:\/var\/lib\/mysql \\\n-e MYSQL_ROOT_PASSWORD=mypass \\\n-e MYSQL_DATABASE=my_data \\\n-e MYSQL_USER=vsftpd \\\n-e MYSQL_PASSWORD=mypass \\\nmariadb:latest\n```\n\nEn este ejemplo, el contenedor puede utilizar hasta 128 MB de memoria. Sin embargo, si el contenedor utiliza m\u00e1s de 64 MB de memoria durante un per\u00edodo prolongado de tiempo, se detendr\u00e1.\n\nEs importante tener en cuenta que los l\u00edmites de recursos para la memoria no son absolutos. El contenedor puede utilizar m\u00e1s memoria de la que se ha establecido si el sistema operativo host tiene memoria disponible. Sin embargo, si el sistema operativo host se queda sin memoria, el contenedor se detendr\u00e1.<\/h3>\n
--memoria<\/code> and --memoria-de-intercambio<\/code> options.<\/p>\n1. Usando
--memoria<\/code><\/h4>\n--memoria<\/code> flag allows you to limit the amount of memory a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can use. If a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> exceeds this limit, it will be killed and potentially restarted if you have a restart policy in place. <\/p>\ndocker run --memory=\"512m\" mi_aplicaci\u00f3n<\/code><\/pre>\n2. Using
--memoria-de-intercambio<\/code><\/h4>\n--memoria-de-intercambio<\/code> option allows you to set a limit on the total amount of memory plus swap a contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can use. If set to -1<\/code>, the contenedor<\/a><\/span>Containers are lightweight, portable units that encapsulate software and its dependencies, enabling consistent execution across different environments. They leverage OS-level virtualization for efficiency. More \u00bb<\/a><\/span><\/span><\/span><\/span><\/span> can use unlimited swap.<\/p>\ndocker run --memory=\"512m\" --memory-swap=\"1g\" my_app<\/code><\/pre>\n