{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/account-for-manual-docker-stops-when-reviewing-restart-policy/", "item": { "id": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/", "slug": "account-for-manual-docker-stops-when-reviewing-restart-policy", "url": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy.md", "json": "https://update.dsesecurity.com/api/v1/posts/account-for-manual-docker-stops-when-reviewing-restart-policy/" }, "title": "Account for manual Docker stops when reviewing restart policy", "summary": "A configured restart policy can intentionally stand aside after an operator stops the container.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-20T18:15:13+00:00", "modified_at": "2026-10-20T18:34:32+00:00", "reviewed_on": "2026-10-20", "reading_minutes": 2, "word_count": 259, "potentially_affected": "Review Docker container restart policy after application exit, operator stop and daemon restart.", "dse_recommendation": "DSE recommends recording deliberate stops in maintenance activity and checking the effective policy before assuming failed automatic recovery.", "primary_source": { "name": "Docker documentation — Start containers automatically", "url": "https://docs.docker.com/engine/containers/start-containers-automatically/", "published_on": null, "authority": "docs.docker.com" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

A configured restart policy can intentionally stand aside after an operator stops the container.

\n

Source facts

\n

Docker ignores a container’s restart policy after a manual stop until the daemon or container is restarted. The always and unless-stopped policies differ across daemon restart: unless-stopped preserves the stopped state. Docker also applies restart policy only after the container has started successfully under its documented monitoring threshold, avoiding an immediate launch-failure loop.

\n

Source: Docker documentation — Start containers automatically.

\n

Applicability

\n

Review Docker container restart policy after application exit, operator stop and daemon restart.

\n

DSE recommendation

\n

DSE recommends recording deliberate stops in maintenance activity and checking the effective policy before assuming failed automatic recovery. Choose whether a stopped workload should return after host maintenance and document that decision with its owner. Avoid combining competing host supervisors and container restart mechanisms without a clear authority. Keep application health checks separate from process-exit handling; a running but unhealthy process may require another response. Review start failures as deployment defects rather than attempting to conceal them with increasingly aggressive restarts.

\n

Verification

\n

In a test workload, compare an application exit with a manual stop, then inspect the result of a controlled daemon restart under the chosen policy. Confirm monitoring recognizes an intentionally stopped service and alerts appropriately when it remains unavailable beyond the approved window. Preserve the operator stop event and the selected policy with the observed lifecycle. Have the service owner identify the permitted maintenance-stop duration and the exact action expected to return the workload to service.

\n

Official reference

\n

Docker documentation — Start containers automatically. Reviewed October 20, 2026.

", "content_text": "A configured restart policy can intentionally stand aside after an operator stops the container.\nSource facts\nDocker ignores a container’s restart policy after a manual stop until the daemon or container is restarted. The always and unless-stopped policies differ across daemon restart: unless-stopped preserves the stopped state. Docker also applies restart policy only after the container has started successfully under its documented monitoring threshold, avoiding an immediate launch-failure loop.\nSource: Docker documentation — Start containers automatically.\nApplicability\nReview Docker container restart policy after application exit, operator stop and daemon restart.\nDSE recommendation\nDSE recommends recording deliberate stops in maintenance activity and checking the effective policy before assuming failed automatic recovery. Choose whether a stopped workload should return after host maintenance and document that decision with its owner. Avoid combining competing host supervisors and container restart mechanisms without a clear authority. Keep application health checks separate from process-exit handling; a running but unhealthy process may require another response. Review start failures as deployment defects rather than attempting to conceal them with increasingly aggressive restarts.\nVerification\nIn a test workload, compare an application exit with a manual stop, then inspect the result of a controlled daemon restart under the chosen policy. Confirm monitoring recognizes an intentionally stopped service and alerts appropriately when it remains unavailable beyond the approved window. Preserve the operator stop event and the selected policy with the observed lifecycle. Have the service owner identify the permitted maintenance-stop duration and the exact action expected to return the workload to service.\nOfficial reference\nDocker documentation — Start containers automatically. Reviewed October 20, 2026.", "content_markdown": "A configured restart policy can intentionally stand aside after an operator stops the container.\n\n## Source facts\n\nDocker ignores a container’s restart policy after a manual stop until the daemon or container is restarted. The always and unless-stopped policies differ across daemon restart: unless-stopped preserves the stopped state. Docker also applies restart policy only after the container has started successfully under its documented monitoring threshold, avoiding an immediate launch-failure loop.\n\nSource: [Docker documentation — Start containers automatically](https://docs.docker.com/engine/containers/start-containers-automatically/).\n\n## Applicability\n\nReview Docker container restart policy after application exit, operator stop and daemon restart.\n\n## DSE recommendation\n\nDSE recommends recording deliberate stops in maintenance activity and checking the effective policy before assuming failed automatic recovery. Choose whether a stopped workload should return after host maintenance and document that decision with its owner. Avoid combining competing host supervisors and container restart mechanisms without a clear authority. Keep application health checks separate from process-exit handling; a running but unhealthy process may require another response. Review start failures as deployment defects rather than attempting to conceal them with increasingly aggressive restarts.\n\n## Verification\n\nIn a test workload, compare an application exit with a manual stop, then inspect the result of a controlled daemon restart under the chosen policy. Confirm monitoring recognizes an intentionally stopped service and alerts appropriately when it remains unavailable beyond the approved window. Preserve the operator stop event and the selected policy with the observed lifecycle. Have the service owner identify the permitted maintenance-stop duration and the exact action expected to return the workload to service.\n\n## Official reference\n\n[Docker documentation — Start containers automatically](https://docs.docker.com/engine/containers/start-containers-automatically/). Reviewed October 20, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/", "url": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-20" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "IT", "item": "https://update.dsesecurity.com/topic/it/" }, { "@type": "ListItem", "position": 3, "name": "Account for manual Docker stops when reviewing restart policy", "item": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/#article", "identifier": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/", "url": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/", "headline": "Account for manual Docker stops when reviewing restart policy", "description": "A configured restart policy can intentionally stand aside after an operator stops the container.", "abstract": "A configured restart policy can intentionally stand aside after an operator stops the container.", "articleBody": "A configured restart policy can intentionally stand aside after an operator stops the container.\nSource facts\nDocker ignores a container’s restart policy after a manual stop until the daemon or container is restarted. The always and unless-stopped policies differ across daemon restart: unless-stopped preserves the stopped state. Docker also applies restart policy only after the container has started successfully under its documented monitoring threshold, avoiding an immediate launch-failure loop.\nSource: Docker documentation — Start containers automatically.\nApplicability\nReview Docker container restart policy after application exit, operator stop and daemon restart.\nDSE recommendation\nDSE recommends recording deliberate stops in maintenance activity and checking the effective policy before assuming failed automatic recovery. Choose whether a stopped workload should return after host maintenance and document that decision with its owner. Avoid combining competing host supervisors and container restart mechanisms without a clear authority. Keep application health checks separate from process-exit handling; a running but unhealthy process may require another response. Review start failures as deployment defects rather than attempting to conceal them with increasingly aggressive restarts.\nVerification\nIn a test workload, compare an application exit with a manual stop, then inspect the result of a controlled daemon restart under the chosen policy. Confirm monitoring recognizes an intentionally stopped service and alerts appropriately when it remains unavailable beyond the approved window. Preserve the operator stop event and the selected policy with the observed lifecycle. Have the service owner identify the permitted maintenance-stop duration and the exact action expected to return the workload to service.\nOfficial reference\nDocker documentation — Start containers automatically. Reviewed October 20, 2026.", "datePublished": "2026-10-20T18:15:13+00:00", "dateModified": "2026-10-20T18:34:32+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/account-for-manual-docker-stops-when-reviewing-restart-policy/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Account for manual Docker stops when reviewing restart policy" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 259, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Docker documentation — Start containers automatically", "url": "https://docs.docker.com/engine/containers/start-containers-automatically/" } } ] } }