{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/", "item": { "id": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/", "slug": "recreate-docker-containers-when-applying-new-json-log-rotation-defaults", "url": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults.md", "json": "https://update.dsesecurity.com/api/v1/posts/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/" }, "title": "Recreate Docker containers when applying new JSON log rotation defaults", "summary": "Editing daemon defaults does not retrofit existing containers’ logging configuration.", "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:07+00:00", "modified_at": "2026-10-20T18:34:32+00:00", "reviewed_on": "2026-10-20", "reading_minutes": 2, "word_count": 255, "potentially_affected": "Review json-file rotation settings on newly created containers and compare existing containers separately.", "dse_recommendation": "DSE recommends inventorying current containers and their effective logging options before declaring rotation complete.", "primary_source": { "name": "Docker documentation — JSON File logging driver", "url": "https://docs.docker.com/engine/logging/drivers/json-file/", "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": "

Editing daemon defaults does not retrofit existing containers’ logging configuration.

\n

Source facts

\n

Docker’s json-file logging driver supports max-size and max-file options for rotation. The documentation states that daemon-level changes take effect for newly created containers after the daemon configuration is applied. Existing containers do not automatically use the new logging configuration. Their effective settings must therefore be checked separately from the host default.

\n

Source: Docker documentation — JSON File logging driver.

\n

Applicability

\n

Review json-file rotation settings on newly created containers and compare existing containers separately.

\n

DSE recommendation

\n

DSE recommends inventorying current containers and their effective logging options before declaring rotation complete. Plan replacement through the workload’s managed deployment procedure so state and availability are preserved. Keep the desired limits in that definition as well as any host default. Compare log production with available disk space and retention needs, and send required historical records to a suitable archive. Track containers intentionally deferred from recreation so a changed default does not create a false sense that all disks are protected.

\n

Verification

\n

Create a disposable container after the configuration change and inspect its driver and rotation options. Compare an older container to demonstrate the difference. Generate only safe test output and verify rotation without modifying daemon-managed files. Confirm the production replacement plan covers every relevant workload. Retain a per-container replacement checklist with the inspected options. Ask the logging owner to approve any intentionally different retention behavior, and keep required archive delivery separate from the local rotation exercise.

\n

Official reference

\n

Docker documentation — JSON File logging driver. Reviewed October 20, 2026.

", "content_text": "Editing daemon defaults does not retrofit existing containers’ logging configuration.\nSource facts\nDocker’s json-file logging driver supports max-size and max-file options for rotation. The documentation states that daemon-level changes take effect for newly created containers after the daemon configuration is applied. Existing containers do not automatically use the new logging configuration. Their effective settings must therefore be checked separately from the host default.\nSource: Docker documentation — JSON File logging driver.\nApplicability\nReview json-file rotation settings on newly created containers and compare existing containers separately.\nDSE recommendation\nDSE recommends inventorying current containers and their effective logging options before declaring rotation complete. Plan replacement through the workload’s managed deployment procedure so state and availability are preserved. Keep the desired limits in that definition as well as any host default. Compare log production with available disk space and retention needs, and send required historical records to a suitable archive. Track containers intentionally deferred from recreation so a changed default does not create a false sense that all disks are protected.\nVerification\nCreate a disposable container after the configuration change and inspect its driver and rotation options. Compare an older container to demonstrate the difference. Generate only safe test output and verify rotation without modifying daemon-managed files. Confirm the production replacement plan covers every relevant workload. Retain a per-container replacement checklist with the inspected options. Ask the logging owner to approve any intentionally different retention behavior, and keep required archive delivery separate from the local rotation exercise.\nOfficial reference\nDocker documentation — JSON File logging driver. Reviewed October 20, 2026.", "content_markdown": "Editing daemon defaults does not retrofit existing containers’ logging configuration.\n\n## Source facts\n\nDocker’s json-file logging driver supports max-size and max-file options for rotation. The documentation states that daemon-level changes take effect for newly created containers after the daemon configuration is applied. Existing containers do not automatically use the new logging configuration. Their effective settings must therefore be checked separately from the host default.\n\nSource: [Docker documentation — JSON File logging driver](https://docs.docker.com/engine/logging/drivers/json-file/).\n\n## Applicability\n\nReview json-file rotation settings on newly created containers and compare existing containers separately.\n\n## DSE recommendation\n\nDSE recommends inventorying current containers and their effective logging options before declaring rotation complete. Plan replacement through the workload’s managed deployment procedure so state and availability are preserved. Keep the desired limits in that definition as well as any host default. Compare log production with available disk space and retention needs, and send required historical records to a suitable archive. Track containers intentionally deferred from recreation so a changed default does not create a false sense that all disks are protected.\n\n## Verification\n\nCreate a disposable container after the configuration change and inspect its driver and rotation options. Compare an older container to demonstrate the difference. Generate only safe test output and verify rotation without modifying daemon-managed files. Confirm the production replacement plan covers every relevant workload. Retain a per-container replacement checklist with the inspected options. Ask the logging owner to approve any intentionally different retention behavior, and keep required archive delivery separate from the local rotation exercise.\n\n## Official reference\n\n[Docker documentation — JSON File logging driver](https://docs.docker.com/engine/logging/drivers/json-file/). 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/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/", "url": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-20" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/#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": "Recreate Docker containers when applying new JSON log rotation defaults", "item": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/#article", "identifier": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/", "url": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/", "headline": "Recreate Docker containers when applying new JSON log rotation defaults", "description": "Editing daemon defaults does not retrofit existing containers’ logging configuration.", "abstract": "Editing daemon defaults does not retrofit existing containers’ logging configuration.", "articleBody": "Editing daemon defaults does not retrofit existing containers’ logging configuration.\nSource facts\nDocker’s json-file logging driver supports max-size and max-file options for rotation. The documentation states that daemon-level changes take effect for newly created containers after the daemon configuration is applied. Existing containers do not automatically use the new logging configuration. Their effective settings must therefore be checked separately from the host default.\nSource: Docker documentation — JSON File logging driver.\nApplicability\nReview json-file rotation settings on newly created containers and compare existing containers separately.\nDSE recommendation\nDSE recommends inventorying current containers and their effective logging options before declaring rotation complete. Plan replacement through the workload’s managed deployment procedure so state and availability are preserved. Keep the desired limits in that definition as well as any host default. Compare log production with available disk space and retention needs, and send required historical records to a suitable archive. Track containers intentionally deferred from recreation so a changed default does not create a false sense that all disks are protected.\nVerification\nCreate a disposable container after the configuration change and inspect its driver and rotation options. Compare an older container to demonstrate the difference. Generate only safe test output and verify rotation without modifying daemon-managed files. Confirm the production replacement plan covers every relevant workload. Retain a per-container replacement checklist with the inspected options. Ask the logging owner to approve any intentionally different retention behavior, and keep required archive delivery separate from the local rotation exercise.\nOfficial reference\nDocker documentation — JSON File logging driver. Reviewed October 20, 2026.", "datePublished": "2026-10-20T18:15:07+00:00", "dateModified": "2026-10-20T18:34:32+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/" }, "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/recreate-docker-containers-when-applying-new-json-log-rotation-defaults/#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": "Recreate Docker containers when applying new JSON log rotation defaults" }, "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": 255, "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 — JSON File logging driver", "url": "https://docs.docker.com/engine/logging/drivers/json-file/" } } ] } }