{"version":"1.0","provider_name":"Profesionales de Docker","provider_url":"https:\/\/dockerpros.com\/es","title":"Docker Compose Down -remove-orphans - Dockerpros","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"o59w67tvkj\"><a href=\"https:\/\/dockerpros.com\/es\/wiki\/docker-compose-down-remove-orphans\/\">Docker Compose Down \u2013remove-orphans\n\nEn el mundo de la contenerizaci\u00f3n, Docker Compose es una herramienta esencial para definir y ejecutar aplicaciones multi-contenedor. A veces, despu\u00e9s de ejecutar `docker-compose down`, es posible que te encuentres con contenedores hu\u00e9rfanos que no se eliminan autom\u00e1ticamente. Aqu\u00ed es donde entra en juego la opci\u00f3n `--remove-orphans`.\n\nCuando ejecutas `docker-compose down --remove-orphans`, Docker Compose no solo detiene y elimina los contenedores definidos en tu archivo `docker-compose.yml`, sino que tambi\u00e9n identifica y elimina cualquier contenedor hu\u00e9rfano que no est\u00e9 definido en tu configuraci\u00f3n actual. Esto es particularmente \u00fatil cuando has eliminado servicios de tu archivo de configuraci\u00f3n o has renombrado contenedores.\n\nEs importante tener en cuenta que esta opci\u00f3n solo afecta a los contenedores. No elimina im\u00e1genes, vol\u00famenes o redes que puedan haber quedado hu\u00e9rfanos. Si necesitas limpiar estos recursos adicionales, deber\u00e1s utilizar otros comandos de Docker.\n\nAdem\u00e1s, ten cuidado al usar esta opci\u00f3n en entornos de producci\u00f3n, ya que podr\u00eda eliminar contenedores que est\u00e1n en uso por otras aplicaciones o servicios que no est\u00e1n definidos en tu archivo `docker-compose.yml` actual.\n\nEn resumen, `docker-compose down --remove-orphans` es una herramienta poderosa para mantener tu entorno Docker limpio y organizado, eliminando eficientemente los contenedores hu\u00e9rfanos que podr\u00edan acumularse con el tiempo.<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/dockerpros.com\/es\/wiki\/docker-compose-down-remove-orphans\/embed\/#?secret=o59w67tvkj\" width=\"600\" height=\"338\" title=\"\u00abDocker Compose Down \u2013remove-orphans\u00bb \u2014 Dockerpros\" data-secret=\"o59w67tvkj\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script>\n\/**\n * WordPress inline HTML embed\n *\n * @since 4.4.0\n * @output wp-includes\/js\/wp-embed.js\n *\n * Single line comments should not be used since they will break\n * the script when inlined in get_post_embed_html(), specifically\n * when the comments are not stripped out due to SCRIPT_DEBUG\n * being turned on.\n *\/\n(function ( window, document ) {\n\t'use strict';\n\n\t\/* Abort for ancient browsers. *\/\n\tif ( ! document.querySelector || ! window.addEventListener || typeof URL === 'undefined' ) {\n\t\treturn;\n\t}\n\n\t\/** @namespace wp *\/\n\twindow.wp = window.wp || {};\n\n\t\/* Abort if script was already executed. *\/\n\tif ( !! window.wp.receiveEmbedMessage ) {\n\t\treturn;\n\t}\n\n\t\/**\n\t * Receive embed message.\n\t *\n\t * @param {MessageEvent} e\n\t *\/\n\twindow.wp.receiveEmbedMessage = function( e ) {\n\t\tvar data = e.data;\n\n\t\t\/* Verify shape of message. *\/\n\t\tif (\n\t\t\t! ( data || data.secret || data.message || data.value ) ||\n\t\t\t\/[^a-zA-Z0-9]\/.test( data.secret )\n\t\t) {\n\t\t\treturn;\n\t\t}\n\n\t\tvar iframes = document.querySelectorAll( 'iframe[data-secret=\"' + data.secret + '\"]' ),\n\t\t\tblockquotes = document.querySelectorAll( 'blockquote[data-secret=\"' + data.secret + '\"]' ),\n\t\t\tallowedProtocols = new RegExp( '^https?:$', 'i' ),\n\t\t\ti, source, height, sourceURL, targetURL;\n\n\t\tfor ( i = 0; i < blockquotes.length; i++ ) {\n\t\t\tblockquotes[ i ].style.display = 'none';\n\t\t}\n\n\t\tfor ( i = 0; i < iframes.length; i++ ) {\n\t\t\tsource = iframes[ i ];\n\n\t\t\tif ( e.source !== source.contentWindow ) {\n\t\t\t\tcontinue;\n\t\t\t}\n\n\t\t\tsource.removeAttribute( 'style' );\n\n\t\t\tif ( 'height' === data.message ) {\n\t\t\t\t\/* Resize the iframe on request. *\/\n\t\t\t\theight = parseInt( data.value, 10 );\n\t\t\t\tif ( height > 1000 ) {\n\t\t\t\t\theight = 1000;\n\t\t\t\t} else if ( ~~height < 200 ) {\n\t\t\t\t\theight = 200;\n\t\t\t\t}\n\n\t\t\t\tsource.height = height;\n\t\t\t} else if ( 'link' === data.message ) {\n\t\t\t\t\/* Link to a specific URL on request. *\/\n\t\t\t\tsourceURL = new URL( source.getAttribute( 'src' ) );\n\t\t\t\ttargetURL = new URL( data.value );\n\n\t\t\t\tif (\n\t\t\t\t\tallowedProtocols.test( targetURL.protocol ) &&\n\t\t\t\t\ttargetURL.host === sourceURL.host &&\n\t\t\t\t\tdocument.activeElement === source\n\t\t\t\t) {\n\t\t\t\t\twindow.top.location.href = data.value;\n\t\t\t\t}\n\t\t\t}\n\t\t}\n\t};\n\n\tfunction onLoad() {\n\t\tvar iframes = document.querySelectorAll( 'iframe.wp-embedded-content' ),\n\t\t\ti, source, secret;\n\n\t\tfor ( i = 0; i < iframes.length; i++ ) {\n\t\t\t\/** @var {IframeElement} *\/\n\t\t\tsource = iframes[ i ];\n\n\t\t\tsecret = source.getAttribute( 'data-secret' );\n\t\t\tif ( ! secret ) {\n\t\t\t\t\/* Add secret to iframe *\/\n\t\t\t\tsecret = Math.random().toString( 36 ).substring( 2, 12 );\n\t\t\t\tsource.src += '#?secret=' + secret;\n\t\t\t\tsource.setAttribute( 'data-secret', secret );\n\t\t\t}\n\n\t\t\t\/*\n\t\t\t * Let post embed window know that the parent is ready for receiving the height message, in case the iframe\n\t\t\t * loaded before wp-embed.js was loaded. When the ready message is received by the post embed window, the\n\t\t\t * window will then (re-)send the height message right away.\n\t\t\t *\/\n\t\t\tsource.contentWindow.postMessage( {\n\t\t\t\tmessage: 'ready',\n\t\t\t\tsecret: secret\n\t\t\t}, '*' );\n\t\t}\n\t}\n\n\twindow.addEventListener( 'message', window.wp.receiveEmbedMessage, false );\n\tdocument.addEventListener( 'DOMContentLoaded', onLoad, false );\n})( window, document );\n\/\/# sourceURL=https:\/\/dockerpros.com\/wp-includes\/js\/wp-embed.js\n<\/script>","thumbnail_url":"https:\/\/dockerpros.com\/wp-content\/uploads\/2024\/07\/docker-compose-down-remove-orphans_1293.jpg","thumbnail_width":800,"thumbnail_height":600,"description":"The `docker-compose down --remove-orphans` command is utilized to stop and remove containers defined in a Compose file, along with any orphaned containers not specified in the current configuration. This ensures a clean environment, helping to avoid conflicts and free up resources."}