DEV Community: Stratos

Fixing Docker Battery Drain on Apple Silicon: Measure, Tune, and Choose Your Stack

Stratos — Fri, 13 Nov 2026 04:45:55 +0000

Disclosure: I build Stratos. This is an updated, AI-assisted adaptation of our original Docker battery guide. It includes Docker's own resource-saving options and does not claim a guaranteed battery improvement from switching tools.

If your MacBook becomes hot or loses charge quickly while developing a Laravel application, Docker may be part of the workload—but it is not enough to see Docker running and assume it is the only cause.

An IDE indexing source files, a frontend watcher rebuilding repeatedly, a queue worker stuck in a retry loop, or a database doing background work can consume resources in either a container-based or a native setup.

The useful sequence is: measure the work, remove what you do not need, then decide whether your project requires containers.

1. Establish a useful baseline

Open Activity Monitor and inspect CPU and Energy while your stack is idle and while you perform representative development tasks. Look at the application and its associated processes, not just one menu-bar process.

Record:

Mac model, chip, memory, macOS, and Docker Desktop version.
The running containers and services.
Whether the laptop is charging, screen brightness, and power settings.
Frontend watchers, queue workers, schedulers, database activity, and IDE indexing.
What you did during the sample and how long you observed it.

Use repeated observations under similar conditions. An Activity Monitor Energy Impact value is a diagnostic signal, not a direct battery-runtime guarantee. A single “0% CPU” sample does not prove a tool never uses CPU.

2. Identify running containers and their work

These commands inspect your setup; they do not delete data:

docker ps
docker stats --no-stream

Check for services you left running from other projects. Inspect repeated application errors, queue retries, and rebuild loops. A quiet web application may still have busy background services.

Stop only containers you recognize and do not currently need. Check running jobs before stopping a worker or database. Do not use volume deletion or aggressive cleanup as a battery troubleshooting step: that can remove development data without explaining the resource use.

3. Check Resource Saver

Docker's Resource Saver documentation describes how it stops the Linux VM after a configurable interval with no containers running. The documented default interval is five minutes, and the feature is enabled by default.

Check Docker Desktop → Settings → Resources for the relevant controls in your installed version. If your database, queue, or other container remains running, the “no running containers” condition has not been met. Resource Saver is not the same as making active container workloads free of resource costs.

If you are done with container work for the day, stopping the unneeded services and letting Resource Saver activate—or quitting Docker Desktop—may be sufficient. You may not need to migrate your project at all.

4. Review filesystem sharing and file watchers

Linux containers on a Mac access host-mounted source through a sharing boundary. The impact depends on Docker's current backend, sharing configuration, and the project's access pattern.

For a PHP project, investigate frequent source scans, dependency access, generated caches, and frontend rebuild activity. Keep watcher scope focused on files that actually need rebuilding. Compare changes one at a time and measure the same request or development task again.

Avoid copying a tuning recipe blindly. Moving files or dependencies into a volume can change how editors, tests, and package managers see them; evaluate that against your team's setup.

5. Decide whether Linux containers are a requirement

Containers remain useful when your application depends on Linux-specific behavior, image-based team environments, or a collection of services defined in Compose. Running PHP directly on macOS does not provide identical Linux behavior or container isolation.

For projects that need local PHP, a database, HTTPS, and development tools without container-specific requirements, a native environment is another option. Removing the Linux VM changes the architecture, but it does not guarantee a particular CPU percentage or battery duration. Native databases, queue workers, and build tools still do real work.

6. Evaluate Stratos with one project

If a native stack fits your requirements:

Keep the project source and development database backed up. Preserve your existing container configuration so you can return to it.
Install Stratos and link the project under Sites. Select the installed PHP version and required extensions.
Start the local services the project actually needs. Configure database host, port, credentials, cache, queue, and mail settings for those services. A Compose service hostname usually will not resolve as a local macOS database address.
Review the site's .test domain and HTTPS configuration. Check Laravel's application URL and any callback URLs.
Run your application's checks: database access, authentication, assets, jobs, scheduled tasks, and tests. Migrate development data deliberately rather than assuming container volumes are automatically imported.
Compare the same workload again. If Linux behavior is required or compatibility differs, retain the container setup for that project.

Stratos's Free edition includes core hosting and selected development tools. Advanced service management and integrated workflows have plan-specific limits; review current pricing before relying on a paid feature.

Stratos 1.7.1 also includes a Free MCP schema bridge for coding agents. It can help an agent inspect permitted table metadata; it does not diagnose battery use automatically. See Local AI & MCP setup.

What a credible battery comparison should publish

If you share before/after results, include hardware, OS/tool versions, the exact application and services, workload, duration, power settings, and repeated measurements. Disclose whether Docker Resource Saver was active and whether containers were still running.

Without those details, fixed claims such as “Docker always uses 15–40% idle CPU,” “native means 0% CPU,” or “switching guarantees all-day battery” are too broad. The practical goal is to reduce unnecessary work while preserving the environment your application needs.

References: Docker Resource Saver, Docker Desktop settings, Stratos installation, and the original guide.

Stratos vs Laravel Herd Pro vs MAMP Pro vs Docker Desktop

Stratos — Thu, 12 Nov 2026 19:43:47 +0000

Disclosure: I build Stratos. This is an updated, AI-assisted adaptation of our original comparison, with links to the other vendors' documentation. It compares workflows rather than claiming that one tool wins every benchmark.

Choosing a local PHP environment starts with your project's requirements. Do you need Linux containers? A Laravel-focused application? A graphical server manager? Or a native Mac stack with debugging tools and a schema bridge for coding agents?

Stratos, Laravel Herd, MAMP Pro, and Docker Desktop overlap, but they solve different parts of that problem.

Compare the workflow first

Area	Stratos	Laravel Herd / Pro	MAMP / MAMP Pro	Docker Desktop
Main approach	Native Swift Mac application managing local PHP and services	Native PHP/Laravel development environment with Free and Pro capabilities	Graphical local web environment; Pro adds site and server configuration workflows	Container development platform; Linux workloads run through a Linux VM on macOS
PHP versions	PHP 8.1–8.5, with per-site selection and simultaneous FPM pools	Version management within its PHP/Laravel workflow; check the current plan comparison	Pro supports individual site/server PHP configurations	Configure PHP images and versions in your container definitions
Local domains and HTTPS	Linked `.test` sites and trusted local HTTPS	Integrated local site workflow	Site configuration through MAMP Pro	Configure your application, ports, certificates, and any reverse proxy
Database workflow	SQLite browser and MySQL basics on Free; broader integrated management and advanced tools depend on the plan	Check current database/service features and plan entitlements	Local database and website management tools	Run databases as services; select a separate client or administration interface as needed
Coding-agent context	Free MCP site/schema context; Pro runtime tools and execution with confirmation	Herd 2.0 advertises agent/runtime context; check current Pro entitlements	Check current vendor integrations for your workflow	Add an appropriate MCP server or integration for the containers/services you use
Debugging and sharing	Integrated mail, dumps, requests, Tinker, profiling, snapshots, and tunnels, with plan-specific limits	Integrated Laravel-oriented tools and services vary by plan	Tools for local website development and testing	Assemble the debugging, mail, profiling, and sharing services your project requires
Container and Linux-image parity	Local macOS services, not Linux container isolation	Local development stack, not a replacement for Linux container isolation	Local web environment, not a container runtime	Suitable when the workflow depends on container images and Linux services

The table describes approaches, not universal feature parity. Vendor releases, operating-system support, and paid entitlements change; check the official pages before choosing a subscription.

Where Stratos fits

Stratos is intended for PHP and Laravel developers who want local macOS services and a single application for common development tasks. You can link a project, choose its installed PHP version, use local HTTPS, and access integrated development tools.

In Stratos 1.7.1, Tools → Local AI & MCP adds a local bridge for Cursor, Claude Code, Claude Desktop, and Windsurf. The Free tools can inspect permitted linked-site metadata and database schema, including columns and foreign keys. They do not return database rows or passwords through the schema API.

Pro adds permitted dumps, request metadata, logs, and performance context. PHP, SQL, and Artisan execution requires confirmation in Stratos, including SQL reads. Approved actions use normal user/project permissions: this is not an operating-system sandbox. Mail and webhook context require separate app-wide permissions.

That distinction matters when choosing an agent workflow. Sharing a schema is a different decision from sharing runtime payloads or allowing execution.

See the MCP setup guide and public example configurations.

Where the alternatives fit

Choose Herd when you want its Laravel-focused workflow and its current integrations suit your projects. Its official site describes a native PHP/Laravel stack. A comparison should evaluate its actual capabilities rather than assume it is an Electron wrapper or that every PHP-version feature requires Pro.

Choose MAMP Pro when its graphical website and server configuration workflow fits your work. MAMP's current product page describes individual server and PHP configurations; describing it as limited to one global PHP version would be misleading.

Choose Docker Desktop when your project or team depends on container definitions, Linux-specific services, or matching image-based environments. A native Mac stack does not reproduce those properties simply by running the same language version.

You can also combine approaches across projects. A container-dependent application and a small native PHP project need not use the same local environment.

Compare resource use on your own workload

Avoid choosing on an unexplained idle CPU screenshot. Compare the same application, service set, request workload, background workers, and filesystem layout. Record hardware, macOS, tool versions, power settings, and test duration.

Docker Desktop also has Resource Saver, which can stop the Linux VM after a period with no running containers. An idle setup with Resource Saver active is different from one with database and worker containers continuously running.

I am not presenting fixed CPU percentages or battery-drain figures here: results depend on workload and configuration, and this article does not include a reproducible benchmark dataset.

Pricing and next steps

Stratos offers a Free edition, Pro at $39/year, Founder Lifetime at $89, and a Team plan. Check current pricing and limits for purchase terms and device allowances. For the other tools, consult their current official pricing rather than treating an old comparison's figures as permanent.

Useful references:

Start with one representative project. Verify PHP extensions, database connectivity, queues, HTTPS, and your team's expected environment before migrating the rest.