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.
Talk to the engineer who will own your stack.
No account managers, no offshore handoff. Senior DevOps, direct. Tell us what you are dealing with and you get a straight answer.
Related News
GitHub 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.
Server & DevOpsGitHub Ships Stacked Pull Requests and One Limitation Decides Whether Your Team Can Actually Use Them
On July 30, 2026 GitHub put stacked pull requests into public preview: an ordered chain of dependent PRs where each layer targets the one below, reviewed separately and merged bottom up, with the branches above rebasing themselves as lower ones land. It is the workflow Graphite built a business on, now native and free. The catch is in the docs rather than the announcement, and it rules the feature out for a whole class of work: all branches must live in the same repository, so cross-fork stacks are not supported at all.
Server & DevOpsOpenAI Is Deleting GPT-5 and o3 in December and the Teams That Pinned Their Models Break First
OpenAI notified developers on June 11, 2026 that six GPT-5 and o3 model snapshots leave the first-party API on December 11, 2026. Teams that pinned an exact dated snapshot ID, OpenAI's own recommended production practice, break loudly on that date, while floating aliases keep working but silently change behavior.