Docker Desktop 4.90.0 Arrives with Docker Agent v1 and Enhanced Virtualization

Docker has officially released Docker Desktop 4.90.0 across macOS, Windows, and Linux distributions. The milestone update introduces Docker Agent v1 alongside substantial refinements to the platform's Virtual Machine Manager (VMM), Enhanced Container Isolation (ECI) controls, and expanded support across multi-architecture environments, including early access for Windows on ARM. Packaged for Apple Silicon, Intel x86_64, Debian, RPM, and Arch ecosystems, the release continues Docker's accelerated cadence aimed at shortening the feedback loop between upstream engine improvements and local developer workflows. For DevOps practitioners, platform architects, and software engineers, this release marks an important operational milestone. As developers increasingly integrate autonomous workflows and language model assistants into daily coding cycles, managing isolated execution boundaries on local machines has become critical. Docker Desktop 4.90.0 directly addresses this by formalizing Docker Agent capabilities while strengthening kernel-level hypervisor boundaries. Teams can run complex multi-container stacks and autonomous tooling without incurring excessive CPU and RAM overhead, all while enforcing fine-grained container isolation that prevents unprivileged local workloads from compromising the host operating system. This update aligns with the broader convergence of container virtualization and AI-assisted software development. Over recent release cycles, Docker has steadily transformed Desktop from a simple daemon wrapper into a comprehensive runtime for both cloud-native microservices and local AI workloads. By modernizing hypervisor backends—such as the container-optimized Docker VMM—and integrating tightly with modern Linux kernel features, Docker ensures that developer environments mirror production container behaviors while maintaining the rapid feedback loop essential for inner-loop development. In practice, platform teams should begin by validating the update against their existing developer workstations, paying close attention to hypervisor backend configurations and enterprise policy enforcement. Windows administrators should verify that target endpoints meet the necessary WSL kernel thresholds or switch to Docker VMM to maximize idle memory reclamation and file I/O throughput. Security engineers should review Enhanced Container Isolation settings and Registry Access Management defaults to ensure seamless compliance before enabling automated updates across organizational fleets.