Docker Desktop 4.36 adds resource saver mode that reduces CPU and memory usage by up to 80% when containers are idle. Key update for developers.
Docker Desktop 4.36 Introduces Resource Saver Mode
Docker has released Docker Desktop 4.36 with a new resource saver mode that automatically reduces CPU and memory consumption when containers are idle. For developers running Docker alongside IDEs and browsers, this addresses the most common complaint - Docker consuming too many system resources.
How Resource Saver Works
When no containers are running active workloads, Docker Desktop now throttles its background processes. The Docker Engine virtual machine reduces its memory allocation and CPU scheduling priority. In testing, this results in 70-80 percent lower resource usage during idle periods.
The feature activates automatically after a configurable idle threshold (default: 5 minutes) and resumes full performance within seconds when containers receive traffic or commands.
Improved Build Performance
Docker Desktop 4.36 also includes BuildKit improvements that speed up multi-stage builds by caching intermediate layers more effectively. For large Magento or Laravel Docker images with multiple build stages, rebuild times can drop by 30-50 percent.
Compose Watch Enhancements
Docker Compose Watch, the file-syncing feature for development workflows, now supports exclude patterns and has reduced file system event latency on macOS. This means faster hot-reload cycles when developing with Docker Compose.
Availability
Docker Desktop 4.36 is available for macOS, Windows, and Linux. The resource saver mode is enabled by default in new installations and can be toggled in Settings for existing users.
Docker Desktop 4.36 is a welcome update for developers who have been frustrated by Docker's resource consumption on macOS and Windows.
Or read how we handle it in DevOps as a Service.
Related News
Kubernetes 1.35 Is the Last Version That Runs containerd 1.x and Most Clusters Have Not Noticed
Kubernetes 1.35, released December 17, 2025, is the last minor release whose runtime support still includes a containerd 1.x version. To upgrade beyond it, every node has to move to containerd 2.x first, and containerd 1.7 itself reaches end of support in September 2026. The trap is not a single date: it is the upgrade path, and most clusters have not noticed because nothing is broken yet.
Server & DevOpsYour CI History Now Expires With Your Build Artifacts
From October 1, GitHub applies your Actions retention setting to checks, workflow runs and statuses, which used to survive 400 days regardless. Anyone who lowered that number to save on artifact storage just signed up to lose their build history at the same interval.
Server & DevOpsGitHub Now Migrates GitLab Repositories in One Command
GitHub Enterprise Importer now handles GitLab migrations self-service, no consulting engagement needed. Repositories, issues, merge requests and releases move with one CLI extension. Here is what comes across, what you rebuild, and how to size the work.