A Deep Dive Into What’s New, Why It Matters, and How It Improves Your Workflow

Docker Desktop for Windows continues to evolve rapidly, and one of the most impactful additions in the recent releases is the new Logs View, which became generally available in version 4.72.0. This feature significantly improves how developers and operators inspect, filter, and troubleshoot container logs — a daily task for anyone working with containers.

In this post, we’ll explore what’s new, why it’s useful, and how it changes the way you work with Docker on Windows.

What Is the New Logs View?

The Logs View is a built‑in, GUI‑based log explorer inside Docker Desktop that allows you to:

– View logs from running or stopped containers
– Filter logs by container, service, or time
– Search within logs
– Tail logs in real time
– Inspect multi‑container logs side‑by‑side (Compose, Swarm, etc.)

While Docker has always provided logs via CLI (`docker logs`), the new Logs View brings a centralized, visual, searchable experience directly into the Desktop UI.

What’s New in the Latest Release?

General Availability (GA)

The Logs View is no longer experimental — it is now a fully supported, production‑ready feature in Docker Desktop for Windows as of 4.72.0.

This means:
– Better stability
– Improved performance
– Full support across Windows installations
– No feature flags required

Improved Windows Installation Options

Alongside the Logs View GA, Docker Desktop for Windows now offers per‑user or all‑user installation modes.

This matters because:
– Logs View behaves consistently across user profiles
– Enterprise environments can standardize deployments
– Permissions and log access become more predictable

Better Reliability and UI Behavior

Recent releases also fixed several UI issues that indirectly improve the Logs View experience, such as:

– More reliable search input behavior in the sidebar
– Improved refresh behavior
– Better handling of background processes

These improvements contribute to a smoother log‑browsing experience.

Why the New Logs View Is Handy?

1. Centralized Troubleshooting

Instead of switching between terminals, containers, and log files, you now get a single pane of glass for all logs.
This is especially useful when:
– Debugging multi‑container apps
– Investigating startup failures
– Monitoring container behavior in real time

2. Faster Debugging With Search & Filters

The Logs View includes:
– Keyword search
– Time‑range filtering
– Container/service filtering

This dramatically reduces the time needed to find relevant log entries.

3. Real‑Time Log Streaming ( I like this one )

You can tail logs live without running `docker logs -f`.

This is ideal for:
– Watching app startup
– Monitoring background jobs
– Observing container health checks

4. Better for Windows‑First Developers

Windows developers often prefer GUI tools.

The Logs View:

– Removes the need for CLI log commands
– Makes Docker more accessible to developers unfamiliar with Linux tooling
– Integrates naturally with the Desktop dashboard

5. Great for Docker Compose Projects

Compose apps generate logs from multiple services.

The Logs View lets you:
– View all logs together
– Or isolate a single service
– Or compare logs side‑by‑side

This is a huge improvement over juggling multiple terminal windows.

Real‑World Use Cases

Debugging a failing container

Instead of running:
————-
docker ps
docker logs <id>
————–

You simply click the container → Logs.

Investigating a multi‑service Compose app

You can instantly see:
– Which service started first
– Which one failed
– How logs correlate in time

Monitoring long‑running tasks

Tail logs visually while keeping your terminal free for other commands.

Onboarding new developers

New team members can inspect logs without learning Docker CLI syntax.

Final Thoughts:

The new Logs View in Docker Desktop for Windows is more than a UI enhancement — it’s a workflow upgrade.
By making logs easier to access, search, and correlate, Docker has significantly improved the day‑to‑day debugging experience for Windows developers and DevOps engineers.
With it’s general availability in 4.72.0, the feature is now stable, polished, and ready for production use.
If you rely on Docker Desktop for development or operations, the new Logs View is absolutely worth exploring

 

Docker Sandbox project.

A Docker sandbox gives you a safe, disposable environment to experiment, build, or let automated tools run without risking your real system. It’s becoming an essential part of modern development workflows, especially as coding agents and cloud‑based tooling evolve. Docker

What a Docker sandbox actually is

A Docker sandbox is an isolated execution environment that behaves like a lightweight, temporary machine. It lets you run containers, install packages, modify configurations, and test ideas freely—while keeping your host system untouched. Modern implementations often use microVMs to provide stronger isolation than traditional containers, giving you the flexibility of a full system with the safety of a sealed box.

Key characteristics include:

• Isolation — Your experiments can’t affect your host OS.
• Disposability — You can reset or destroy the environment instantly.
• Reproducibility — Every sandbox starts from a known, clean state.
• Autonomy — Tools and agents can run unattended without permission prompts.

Why Docker sandboxes matter now

The rise of coding agents and automated development tools has created new demands. These agents need to run commands, install dependencies, and even use Docker themselves. Traditional approaches—like OS‑level sandboxing or full virtual machines—either interrupt workflows or are too heavy. Docker sandboxes solve this by offering:

• A real system for agents to work in
• The ability to run Docker inside the sandbox
• A consistent environment across platforms
• Fast resets for iterative development

This makes them ideal for AI‑assisted coding, CI/CD experimentation, and secure testing.

Where you can use Docker sandboxes today

Several platforms now offer browser‑based or cloud‑hosted Docker sandboxes, making it easy to experiment without installing anything locally.

• Docker Sandboxes (Docker Inc.) — Purpose‑built for coding agents, using microVM isolation.
• CodeSandbox Docker environments — Interactive online playgrounds where you can fork, edit, and run Docker‑based projects directly in the browser. CodeSandbox
• LabEx Online Docker Playground — A full Docker terminal running on Ubuntu 22.04, ideal for learning and hands‑on practice, especially as Play with Docker winds down. LabEx

These platforms remove setup friction and let you focus on learning, testing, or building.

How developers typically use Docker sandboxes

A Docker sandbox fits naturally into several workflows:

• Learning Docker — Practice commands, build images, and explore networking without installing anything.
• Testing risky changes — Try new packages, configs, or scripts without fear of breaking your machine.
• Running coding agents — Give AI tools a safe environment to operate autonomously.
• Prototyping microservices — Spin up isolated services quickly and tear them down just as fast.
• Teaching and workshops — Provide a consistent environment for all participants.

A non‑obvious advantage

Docker sandboxes aren’t just about safety—they’re about speed of iteration. Because they reset instantly and start from a known state, they eliminate the “works on my machine” problem and make experimentation frictionless. This is especially powerful when combined with automated tools or when onboarding new team members.

Closing thought

Docker sandboxes are becoming a foundational tool for modern development—combining safety, speed, and autonomy in a way that traditional containers or VMs alone can’t match. They’re especially valuable if you’re experimenting with AI‑driven coding tools or want a clean, reproducible environment for testing.
Important: Use Docker Sandboxes for testing.

Claude Code sandbox

It works great with VSCode and with Copilot.

More information about Docker Sandbox

 

Azure Local Cluster on‑site working in tandem with Azure Cloud, running Dockerized AI workloads at the edge — is not just viable. It’s exactly the direction modern distributed AI systems are heading.

Let me unpack how these pieces fit together and why the architecture is so compelling.

Azure Local Baseline reference Architecture

A powerful hybrid model for real‑world AI

Think of this setup as a two‑layer AI fabric:

• Layer 1: On‑site Azure Local Cluster
  Handles real‑time inference, local decision‑making, and data preprocessing.
  This is where Docker containers shine: predictable, isolated, versioned workloads running close to the data source.
• Layer 2: Azure Cloud
  Handles heavy lifting: model training, analytics, fleet management, OTA updates, and long‑term storage.

Together, they create a system that is fast, resilient, secure, and scalable

Why this architecture works so well

1. Ultra‑low latency inference

Your on‑site Azure Local Cluster can run Dockerized AI models directly on edge hardware (Jetson, x86, ARM).
This eliminates cloud round‑trips for:

• object detection
• anomaly detection
• robotics control
• industrial automation

Azure Local provides the core platform for hosting and managing virtualized and containerized workloads on-premises or at the edge.

2. Seamless model lifecycle management

Azure Cloud can:

• train new models
• validate them
• push them as Docker images
• orchestrate rollouts to thousands of edge nodes

Your local cluster simply pulls the new container and swaps it in.
This is exactly the “atomic update” pattern from the blogpost.

3. Strong separation of concerns

Local cluster = deterministic, real‑time execution
Cloud = dynamic, scalable intelligence

This separation avoids the classic problem of trying to run everything everywhere.

4. Enterprise‑grade security

Azure Arc, IoT Edge, and Container Registry gives you:

• signed images
• policy‑based deployments
• identity‑bound devices
• encrypted communication

This is critical when edge devices live in factories, stores, or public spaces.

5. Cloud‑assisted intelligence

Even though inference happens locally, the cloud can still:

• aggregate telemetry
• retrain models
• detect drift
• optimize pipelines
• coordinate multi‑site deployments

This is how AI systems improve over time. 

How Docker fits into this hybrid world

Docker becomes the unit of deployment across both environments for DevOps and developers.

On the edge:

• lightweight images
• Hardened images
• GPU‑enabled containers
• read‑only root filesystems
• offline‑capable workloads

In the cloud:

• CI/CD pipelines
• model registries
• automated scanning
• versioned releases

The same container image runs in both places — but with different responsibilities.

My take: This is one of the strongest architectures for real‑world AI

If your goal is:

• real‑time AI
• high reliability
• centralized control
• scalable deployments
• secure operations
• hybrid cloud + edge synergy

…then Azure Local Cluster + Azure Cloud + Docker AI Edge is a near‑ideal solution.

It gives you the best of both worlds:
cloud intelligence + edge autonomy.

Here you find more about Microsoft Azure Local 

Here you find more blogposts about Docker, Windows Server 2025, and Azure Cloud Services :

Windows Server 2025 Core and Docker – A Modern Container Host Architecture

Docker Desktop Container Images and Azure Cloud App Services

The Rise of Free Hardened Docker Images: A New Security Baseline for Developers and DevOps

Containerization has become the backbone of modern software delivery. But as adoption has exploded, so has the attack surface. Vulnerable base images, outdated dependencies, and misconfigured runtimes have quietly become some of the most common entry points for supply‑chain attacks.

The industry has been asking for a better baseline—something secure by default, continuously maintained, and frictionless for teams to adopt. And now we’re finally seeing it: free hardened Docker images becoming widely available from major vendors and open‑source security communities.

This shift isn’t just a convenience upgrade. It’s a fundamental change in how we think about container security.

Why Hardened Images Matter More Than Ever

A “hardened” image isn’t just a slimmer version of a base OS. It’s a container that has been:

• Stripped of unnecessary packages
  Fewer binaries = fewer vulnerabilities.
• Built with secure defaults
  Non‑root users, locked‑down permissions, and minimized attack surface.
• Continuously scanned and patched
  Automated pipelines ensure CVEs are fixed quickly.
• Cryptographically signed
  So you can verify provenance and integrity before deployment.
• Aligned with compliance frameworks
  CIS Benchmarks, NIST 800‑190, and other standards are increasingly baked in.

For developers, this means fewer surprises during security reviews. For DevOps teams, it means fewer late‑night patch cycles and fewer emergency rebuilds.

What’s New About the Latest Generation of Free Hardened Images

The newest wave of hardened images goes far beyond the “minimal OS” approach of the past. Here’s what’s changing:

1. Hardened Language Runtimes

We’re seeing secure-by-default images for:

• Python
• Node.js
• Go
• Java
• .NET
• Rust

These images often include:

• Preconfigured non‑root users
• Read‑only root filesystems
• Mandatory access control profiles
• Reduced dependency trees

2. Automated SBOMs (Software Bills of Materials)

Every image now ships with a machine‑readable SBOM.
This gives you:

• Full visibility into dependencies
• Faster vulnerability triage
• Easier compliance reporting

SBOMs are no longer optional—they’re becoming a standard part of secure supply chains.

3. Built‑in Image Signing and Verification

Tools like Sigstore Cosign, Notary v2, and Docker Content Trust are now integrated directly into image pipelines.

This means you can enforce:

• “Only signed images may run” policies
• Zero‑trust container admission
• Immutable deployment guarantees

4. Continuous Hardening Pipelines

Instead of waiting for monthly rebuilds, hardened images are now updated:

• Daily
• Automatically
• With CVE‑aware rebuild triggers

This dramatically reduces the window of exposure for newly discovered vulnerabilities.

Read the complete blogpost about a Safer Container Ecosystem with Docker: Free Docker Hardened Images here

Docker Desktop continues to evolve as the go-to platform for containerized development, and the latest release — version 4.51.0 — brings exciting new capabilities for developers working with Kubernetes.

What’s New in 4.51.0

1. Kubernetes Resource Setup Made Simple

One of the standout features in this release is the ability to set up Kubernetes resources directly from a new view inside Docker Desktop. This streamlined interface allows developers to configure pods, services, and deployments without leaving the Desktop environment. It’s a huge step toward making Kubernetes more approachable for teams who want to focus on building rather than wrestling with YAML files.

2. Real-Time Kubernetes Monitoring

The new Kubernetes view also provides a live display of your cluster state. You can now see pods, services, and deployments update in real time, making it easier to spot issues, monitor workloads, and ensure everything is running smoothly.

3. Smarter Dependency Management

Docker Desktop now integrates improvements with Kind (Kubernetes in Docker), ensuring that only required dependency images are pulled if they aren’t already available locally. This reduces unnecessary downloads and speeds up cluster setup.

4. Updated Core Components

• Docker Engine v28.5.2 ships with this release, ensuring stability and performance improvements.
• Enhanced Linux kernel support for smoother Kubernetes operations.

Why This Matters

Kubernetes has a reputation for being complex for some people, but Docker Desktop 4.51.0 is working to change that. By embedding Kubernetes resource management and monitoring directly into the Desktop experience, Docker is lowering the barrier to entry for developers and teams. Whether you’re experimenting with microservices or managing production-like environments locally, these new features make Kubernetes more accessible and intuitive.

Getting Started

To try out these new features:

1. Update to Docker Desktop 4.51.0.
2. Open the new Kubernetes view to configure resources.
3. Watch your pods, services, and deployments update in real time.

Update available with New Kubernetes UI
Click on Download Update

Click on Create Cluster

Here you can select a Single Node Cluster or with Kind a Multi-Node Cluster.
I selected for a Single node cluster.

Click on Install

Here is your Single Node Kubernetes Cluster running with version 1.34.1

Kubectl get nodes

My Nginx Container app is running on Kubernetes in Docker Desktop

Final Thoughts

Docker Desktop 4.51.0 is more than just an incremental update — it’s a meaningful step toward bridging the gap between container development and Kubernetes orchestration. With simplified setup and real-time monitoring, developers can spend less time configuring and more time innovating.

Here you find more information about Docker Desktop and Kubernetes Clustering

 

Docker Desktop and Azure App Cloud Services

Expanded Architecture: Docker developer environment with Azure Cloud Services.

Development Environment

• Docker Desktop + Tools: Visual Studio Code, Azure CLI, Docker Scout, AI, MCP
• Docker Scout CLI: Compares image versions, detects CVEs, integrates with pipelines

Container Host (Windows Server 2025 Core)

• Hyper-V Isolated Containers: For enhanced security
• Workloads: Microservices, legacy apps, AI containers
• GitOps Operator: Automated deployment via Git repositories
• Azure Arc Agent: Connects on-prem host to Azure Control Plane

Here you find more information about Docker on Windows Server 2025 Core

Your Windows 11 Laptop with Docker Desktop

• Hyper-V / WSL2: for your containers development
• Azure Arc Agent: for your Azure Cloud Services and security
• Docker Desktop for Windows installed

Azure Cloud Integrations

Component	Function
Azure App Service (Docker)	Hosts web apps as Docker containers with autoscaling and Key Vault integration
Azure DevOps + Pipelines	CI/CD for image build, scan, push, and deployment
Azure Copilot Security	AI-driven security recommendations and policy analysis
Azure Container Registry (ACR)	Secure storage and distribution of container images
Azure Key Vault	Secrets management: API keys, passwords, certificates
Microsoft Defender for Cloud	Runtime protection, image scanning, threat detection
Azure Policy & RBAC	Governance and access control
Azure Monitor + Sentinel	Logging, metrics, threat detection
Azure Update Manager	Hotpatching of Windows and container images without reboot

More information on Strengthening Container Security with Docker Hardened Images and Azure Container Registry

DevSecOps Workflow

1. Build & Harden Image → Dockerfile + SBOM
2. Scan with Docker Scout → CLI or pipeline
3. Push to ACR → With signing and RBAC
4. Deploy via Azure DevOps Pipelines → App Service or Arc-enabled host
5. Inject Secrets via Key Vault → Automatically at runtime
6. Monitor & Patch → Azure Monitor + Update Manager
7. Audit & Alerting → Azure Sentinel + Defender
8. Security Guidance → Copilot Security analyzes policies and offers recommendations

Example of Deploying a custom container to Azure App Service with Azure Pipelines

Microsoft Azure App Service is really scalable for Docker App Solutions:

Azure App Service is designed to scale effortlessly with your application’s needs. Whether you’re hosting a simple web app or a complex containerized microservice, it offers both vertical scaling (upgrading resources like CPU and memory) and horizontal scaling (adding more instances). With built-in autoscaling, you can respond dynamically to traffic spikes, scheduled workloads, or performance thresholds—without manual intervention or downtime.

From small startups to enterprise-grade deployments, App Service adapts to demand with precision, making it a reliable platform for modern, cloud-native applications.

Scale Up Features and Capacities Learn how to increase CPU, memory, and disk space by changing the pricing tier

Enable Automatic Scaling (Scale Out) Configure autoscaling based on traffic, schedules, or resource metrics

Per-App Scaling for High-Density Hosting Scale individual apps independently within the same App Service Plan

Conclusion

For modern developers, the combination of Azure App Services and Docker Desktop offers a powerful, flexible, and scalable foundation for building, testing, and deploying cloud-native applications.

• Developers can build locally with Docker, ensuring consistency and portability.
• Then deploy seamlessly to Azure App Services, leveraging its cloud scalability and integration.
• This workflow reduces configuration drift, accelerates testing cycles, and improves team collaboration.

As businesses race toward cloud-native infrastructure and microservices, Windows Server 2025 Core emerges as a lean, powerful platform for hosting Docker containers. With its minimal footprint and robust security posture, Server Core paired with Docker offers a compelling solution for modern application deployment.

Architecture Design: Windows Server Core + Docker

Windows Server 2025 Core is a headless, GUI-less version of Windows Server designed for performance and security. When used as a Docker container host, it provides:

• Lightweight OS footprint: Reduces attack surface and resource consumption.
• Hyper-V isolation: Enables secure container execution with kernel-level separation.
• Support for Nano Server and Server Core images: Ideal for running Windows-based microservices.
• Integration with Azure Kubernetes Service (AKS): Seamless orchestration in hybrid environments.

Key Components

Component	Role in Architecture
Windows Server 2025 Core	Host OS with minimal services
Docker Engine	Container runtime for managing containers
Hyper-V	Optional isolation layer for enhanced security
PowerShell / CLI Tools	Management and automation
Windows Admin Center	GUI-based remote management

Installation Guide

Setting up Docker on Windows Server 2025 Core is straightforward but requires precision. Here’s a simplified walkthrough:

Windows Server 2025 Datacenter Core running

1. Install Required Features

Use PowerShell to install Hyper-V and Containers features:

Install-WindowsFeature -Name Hyper-V, Containers -IncludeManagementTools -Restart

2. Install Docker

Download and install Docker from the official source or use the PowerShell script provided by Microsoft:

Invoke-WebRequest “https://download.docker.com/win/static/stable/x86_64/docker-28.4.0.zip&#8221; -OutFile “docker.zip”

Unzip and configure Docker as a service:

at Docker directory to your path

Add the Docker config directory

Set the daemon

Create the Docker Service

net start docker

docker version

Docker Host on Windows Server 2025 Core is Installed

3. Configure Networking

Ensure proper NAT or transparent networking for container communication.

4. Pull Base Images

Use Docker CLI to pull Windows container images:

docker pull mcr.microsoft.com/windows/servercore:ltsc2025

5. Test Deployment

Run a sample Windows Server 2025 core container:

docker run -it mcr.microsoft.com/windows/servercore:ltsc2025

Inside the Windows Server 2025 Core Container on the Docker host.

Best Practices

To maximize reliability, security, and scalability:

• Use Hyper-V isolation for sensitive workloads.
• Automate deployments with PowerShell scripts or CI/CD pipelines.
• Keep base images updated to patch vulnerabilities.
• Monitor containers using Azure Arc monitoring or Windows Admin Center.
• Limit container privileges and avoid running as Administrator.
• Use volume mounts for persistent data storage.

Conclusion: Why It Matters

For developers, Windows Server 2025 Core with Docker offers:

• Fast iteration cycles with isolated environments.
• Consistent dev-to-prod workflows using container images.
• Improved security with minimal OS footprint and Hyper-V isolation.

For businesses, the benefits are even broader:

• Reduced infrastructure costs via efficient resource usage.
• Simplified legacy modernization by containerizing Windows apps.
• Hybrid cloud readiness with Azure integration and Kubernetes support.
• Scalable architecture for microservices and distributed systems.

Windows Server 2025 Core isn’t just a server OS—it’s a launchpad for modern, secure, and scalable containerized applications. Whether you’re a developer building the next big thing or a business optimizing legacy systems, this combo is worth the investment.

Integrating Azure Arc into the Windows Server 2025 Core + Docker Architecture for Adaptive Cloud

Overview

Microsoft Azure Arc extends Azure’s control plane to your on-premises Windows Server 2025 Core container hosts. By onboarding your Server Core machines as Azure Arc–enabled servers, you gain unified policy enforcement, monitoring, update management, and GitOps-driven configurations—all while keeping workloads close to the data and users.

Architecture Extension

• Azure Connected Machine Agent
  Installs on Windows Server 2025 Core as a Feature on Demand, creating an Azure resource that represents your physical or virtual machine in the Azure portal.
• Control Plane Integration
  Onboarded servers appear in Azure Resource Manager (ARM), letting you apply Azure Policy, role-based access control (RBAC), and tag-based cost tracking.
• Hybrid Monitoring & Telemetry
  Azure Monitor collects logs and metrics from Docker Engine, container workloads, and host-level performance counters—streamlined into your existing Log Analytics workspaces.
• Update Management & Hotpatching
  Leverage Azure Update Manager to schedule Windows and container image patches. Critical fixes can even be applied via hotpatching on Arc-enabled machines without a reboot.
• GitOps & Configuration as Code
  Use Azure Arc–enabled Kubernetes to deploy container workloads via Git repositories, or apply Desired State Configuration (DSC) policies to Server Core itself.

Adaptive Cloud Features Enabled

• Centralized Compliance
  Apply Azure Policies to enforce security baselines across every Docker host, ensuring drift-free configurations.
• Dynamic Scaling
  Trigger Azure Automation runbooks or Logic Apps when performance thresholds are breached, auto-provisioning new container hosts.
• Unified Security Posture
  Feed security alerts from Microsoft Defender for Cloud into Azure Sentinel, correlating threats across on-prem and cloud.
• Hybrid Kubernetes Orchestration
  Extend AKS clusters to run on Arc-connected servers, enabling consistent deployment pipelines whether containers live on Azure or in your datacenter.

More information about Innovate on an Adaptive Cloud here

Integration Walkthrough

1. Prepare your Server Core host (ensure Hyper-V, Containers, and Azure Arc Feature on Demand are installed).
2. Install Azure Arc agent via Azure PowerShell
3. In the Azure portal, navigate to Azure Arc > Servers, and verify your machine is onboarded.
4. Enable Azure Policy assignments, connect to a Log Analytics workspace, and turn on Update Management.
5. (Optional) Deploy the Azure Arc GitOps operator for containerized workloads across hybrid clusters.

Visualizing Azure Arc in Your Diagram

Above your existing isometric architecture, add a floating “Azure Cloud Control Plane” layer that includes:

• ARM with Policy assignments
• Azure Monitor / Log Analytics
• Update Manager + Hotpatch service
• GitOps repo integrations

Draw data and policy-enforcement arrows from this Azure layer down to your Windows Server Core “building,” Docker cube, container workloads, and Hyper-V racks—demonstrating end-to-end adaptive management.

Why It Matters

Integrating Azure Arc transforms your static container host into an adaptive cloud-ready node. You’ll achieve:

• Consistent governance across on-prem and cloud
• Automated maintenance with zero-downtime patching
• Policy-driven security at scale
• Simplified hybrid Kubernetes and container lifecycle management

With Azure Arc, your Windows Server 2025 Core and Docker container hosts become full citizens of the Azure ecosystem—securing, monitoring, and scaling your workloads wherever they run.

Better Together

 

Docker Scout version 1.18.2

There’s a quiet moment after every deploy where you ask yourself: what actually changed? Not just the feature—you know that—but the stuff beneath it. Packages. Base images. Vulnerabilities that slipped in while you were busy shipping. Docker Scout’s CLI gives you the flashlight for that dark room. No dashboards. No detours. Just commands, signal, and the truth.

In July 2025 I wrote a blogpost about Docker Scout for Vulnerability management of Containers and remediation

Docker Scout Compare is quite significant for container security, especially in modern DevSecOps workflows. Here’s why it matters:

What Docker Scout Compare Does

• Image Comparison: It analyzes two Docker images—typically a new build vs. a production version—and highlights differences in vulnerabilities, packages, and policies.
• Security Insights: It identifies newly introduced CVEs (Common Vulnerabilities and Exposures), changes in package versions, and policy violations between image versions.
• SBOM Integration: It uses Software Bill of Materials (SBOMs) to trace dependencies and match them against vulnerability databases.

Why It’s Important for Security

• Proactive Risk Management: By comparing images before deployment, teams can catch regressions or newly introduced vulnerabilities early.
• Supply Chain Transparency: Helps track changes across the container supply chain, which is crucial for preventing issues like Log4Shell.
• CI/CD Integration: Fits seamlessly into automated pipelines, ensuring every image update is vetted for security before release.

Key Features That Boost Its Value

Feature	Benefit
Continuous vulnerability scanning	Keeps your images secure over time, not just at build time
Filtering options	Focus on critical or fixable CVEs, ignore unchanged packages, etc.
Markdown/Text reports	Easy to integrate into documentation or dashboards
Multi-stage build analysis	Understand security across complex Dockerfiles

Bottom Line

If you’re serious about container security, Docker Scout Compare isn’t just helpful—it’s becoming essential. It gives developers and security teams a clear view of what’s changing and whether those changes introduce risk.

The heart of change: compare old vs new, precisely

You built a new image. What did you add? What did you remove? What got better—or worse?
Here are some Docker scout compare CLI commands:

# Compare prod vs new build

docker scout compare –to myapp:prod myapp:sha-123

# Focus on meaningful risk changes (ignore base image CVEs)

docker scout compare –to myapp:prod myapp:sha-123 –ignore-base

# Show only high/critical that are fixable

docker scout compare –to myapp:prod myapp:sha-123 –only-severity high,critical –only-fixed

# Fail when security gets worse (perfect for CI)

docker scout compare –to myapp:prod myapp:sha-123 –exit-on vulnerability

Here you find more about Docker Scout Compare

In my case I will do a Docker Scout compare between these two images:

docker scout compare –to azure-cli-patched:latest mcr.microsoft.com/azure-cli:azurelinux3.0

Compare results between the two images.

Compare results between the two images, here you see the Fixed vulnerability differences.

Conclusion

Final Thoughts: Docker Scout Compare CLI & Security

In today’s fast-paced development landscape, security can’t be an afterthought—it must be woven into every stage of the software lifecycle. Docker Scout Compare CLI empowers teams to do just that by offering a clear, actionable view of how container images evolve and what risks they may introduce. Its ability to pinpoint new vulnerabilities, track dependency changes, and integrate seamlessly into CI/CD pipelines makes it a vital tool for modern DevSecOps.

By embracing Docker Scout Compare, organizations move from reactive patching to proactive prevention—turning container security from a bottleneck into a strategic advantage.

I have installed the latest Docker Desktop for Windows version 4.43.2

In today’s cloud-native world, container security is not a luxury—it’s a mission-critical requirement. With the release of Azure Linux 3.0, Microsoft has reinforced its dedication to performance, flexibility, and security. But no matter how polished the host OS is, containers themselves can still be riddled with vulnerabilities, bloated layers, or sneaky outdated dependencies. That’s where Docker Scout and Open Source tool Dive come into play.

Docker Scout: Intelligence at Your Fingertips

Docker Scout introduces vulnerability detection into your CI/CD pipeline. For Azure Linux 3.0 containers, this means:

• Real-Time Vulnerability Scanning: Scout analyzes your container image (including base layers) against CVE databases and flags known vulnerabilities.
• Remediation Guidance: It doesn’t just scream “VULNERABLE!”—Scout offers actionable suggestions like switching to a newer base image or updating specific packages.
• Policy Integration: You can define security policies (e.g., block images with critical CVEs) and automate enforcement in Azure DevOps or GitHub Actions.

In the following steps we will get the Microsoft Azure Linux 3.0 container and scan for security issues before we run the container.

Open Docker terminal
docker pull mcr.microsoft.com/azure-cli:azurelinux3.0

when you have pulled the image, you can do a quick scan with Docker Scout.
docker scout quickview mcr.microsoft.com/azure-cli:azurelinux3.0

docker scout cves mcr.microsoft.com/azure-cli:azurelinux3.0

Here you can see more information about the CVE’s.

Here you see the vulnerable package file and the fix for remediation.

Now we want to remediate this image with the update fix version 2.32.4 of this package. To do this, I made a directory docker fix with a dockerfile (without any extension) with the following commands :

———

# Start met Azure CLI base image op Azure Linux 3.0
FROM mcr.microsoft.com/azure-cli:azurelinux3.0

# Install Python and pip via tdnf
RUN tdnf install -y python3 python3-pip

# Upgrade pip and install
RUN python3 -m pip install –no-cache-dir –upgrade –ignore-installed pip \
&& python3 -m pip install –no-cache-dir requests==2.32.4

# Remove old files
RUN rm -f /usr/lib/az/lib/python3.12/site-packages/requests-2.32.3.dist-info/METADATA

# Verify 
RUN python3 -c “import requests; print(f’Requests versie: {requests.__version__}’)”

————-

With Open Source tool Dive you can have a look into the Docker image. This supported me because first I did only the install and upgrade of the file requests version 2.32.3 to fixed version 2.32.4. But then Docker Scout still see the vulnerability file in the image.

dive [Image]
So that’s why we remove it via the Dockerfile.

We now building a new image with this dockerfile :

docker buildx build –provenance=true –sbom=true -t azure-cli-patched:latest .

After a Docker Scout scan, there are zero vulnerabilities in the image now
and in the Container fixed version 2.32.4 is running.

Conclusion

Docker Scout represents a major leap forward in managing container security, efficiency, and reliability. By integrating seamlessly into the Docker ecosystem, it empowers developers to ship production-ready containers with confidence.

Key Benefits

• Security Insights: Automatically detects vulnerabilities, recommends fixes, and integrates with CVE databases.
• Dependency Intelligence: Tracks changes and upgrades across your software stack to ensure compatibility and stability.
• Image Comparison: Visualizes differences between builds—helping you pinpoint unintended changes and regressions.
• Team Collaboration: Enables shared visibility across development pipelines, so teams can align on image quality and release standards.

In short, Docker Scout turns container image analysis into a proactive, collaborative part of modern DevOps. Whether you’re optimizing performance or hardening against threats, Scout puts you ahead of the curve.

 

 

 

Docker Desktop version 4.41 available

Unleashing AI Development with Docker Desktop 4.41: NVIDIA GPU Support and Model Runner Beta

The world of AI development is evolving rapidly, and Docker Desktop 4.41 is here to accelerate that journey. With the introduction of the Model Runner Beta and NVIDIA GPU support, Docker has taken a significant leap forward in making AI development more accessible, efficient, and integrated. Let’s dive into the highlights of this groundbreaking release.

What’s New in Docker Desktop 4.41?

Docker Desktop 4.41 introduces the Model Runner Beta, a feature designed to simplify the process of running and managing AI models locally. This release also brings NVIDIA GPU support to Windows users, enabling developers to harness the power of GPU acceleration for their machine learning tasks. Here’s a closer look at the key updates:

1. Model Runner Beta:
   • The Model Runner Beta allows developers to run AI models as part of their Docker Compose projects. This integration streamlines the orchestration of model pulls and the injection of model runner services into applications.
   • A dedicated “Models” section in the Docker Desktop GUI provides a user-friendly interface for browsing, running, and managing models alongside containers, volumes, and images.
2. NVIDIA GPU Support:
   • Windows users can now leverage NVIDIA GPUs for AI workloads, significantly boosting performance and reducing training times for machine learning models.
   • This feature is a game-changer for developers working on resource-intensive AI applications, as it enables seamless integration of GPU acceleration into their workflows.
3. Enhanced Integration with Docker Compose and Testcontainers:
   • Docker Compose now supports the declaration of AI services within a single Compose file, allowing teams to manage models like any other service in their development environment.
   • Testcontainers integration extends testing capabilities to AI models, with initial support for Java and Go, making it easier to create automated tests for AI-powered applications.

Why This Matters for AI Developers

The introduction of the Model Runner Beta and NVIDIA GPU support in Docker Desktop 4.41 addresses several pain points faced by AI developers:

• Simplified Workflows: By treating models as first-class artifacts, Docker enables developers to version, distribute, and deploy models using familiar tools and workflows.
• Improved Performance: GPU acceleration ensures faster training and inference times, allowing developers to iterate and innovate more quickly.
• Seamless Collaboration: The ability to push models directly to Docker Hub fosters collaboration and sharing across teams, eliminating the need for custom registries or additional infrastructure.

Getting Started with Docker Model Runner

Enable GPU-backed Inference

docker model status

docker model help

docker model pull ai/smollm2

ai/smollm2 model pulled successfully

docker model list

docker model run ai/smollm2

This is a small example, but it’s really fast with answering my questions

The Future of AI Development with Docker

Docker Desktop 4.41 is more than just an update; it’s a step towards democratizing AI development. By integrating powerful tools like the Model Runner Beta and NVIDIA GPU support, Docker is empowering developers to build, test, and deploy AI applications with unprecedented ease and efficiency.

Whether you’re a seasoned AI researcher or a developer exploring the possibilities of machine learning, Docker Desktop 4.41 is your gateway to a faster, smarter, and more collaborative AI development experience.

Ready to transform your AI workflows? Dive into Docker Desktop 4.41 and experience the future of AI development today!

Docker Desktop for Windows update 4.39.0

Introduction
Docker Desktop 4.39.0 is here, bringing a host of new features designed to enhance developer productivity, streamline workflows, and improve security. This release continues Docker’s commitment to providing efficient, secure, and reliable tools for building, sharing, and running applications.

Key Features in Docker Desktop 4.39.0

1. Docker AI Agent with Model Context Protocol (MCP) and Kubernetes Support
   • The Docker AI Agent, introduced in previous versions, has been upgraded to support MCP and Kubernetes. MCP enables AI-powered applications to access external data sources, perform operations with third-party services, and interact with local filesystems. Kubernetes support allows the AI Agent to manage namespaces, deploy services, and analyze pod logs.
2. General Availability of Docker Desktop CLI
   • The Docker Desktop CLI is now officially available, offering developers a powerful command-line interface for managing containers, images, and volumes. The new docker desktop logs command simplifies log management.
3. Platform Flag for Multi-Platform Image Management
   • Docker Desktop now supports the –platform flag on docker load and docker save commands, enabling seamless import and export of multi-platform images.
4. Enhanced Containerization Across Programming Languages
   • The Docker AI Agent can now containerize applications written in JavaScript, Python, Go, C#, and more. It analyzes projects to identify services, programming languages, and package managers, making containerization effortless.
5. Security Improvements
   • Docker Desktop 4.39.0 addresses critical vulnerabilities, such as CVE-2025-1696, ensuring proxy authentication credentials are no longer exposed in plaintext.

Docker Scout Security

Why These Features Matter

• Developer Productivity: The upgraded Docker AI Agent simplifies container management and troubleshooting, saving developers time and effort.
• Multi-Platform Flexibility: The –platform flag ensures compatibility across diverse environments, making Docker Desktop a versatile tool for modern development.
• Enhanced Security: By addressing vulnerabilities, Docker Desktop 4.39.0 reinforces its position as a secure platform for application development.

Conclusion
Docker Desktop 4.39.0 is a significant step forward, offering smarter tools, improved security, and greater flexibility for developers. Whether you’re managing Kubernetes clusters or containerizing applications, this release has something for everyone.

For more details, you can explore the official Docker blog or the release notes

 

Install the Newest Docker Desktop version 4.38.0

Docker released a New Docker Desktop version 4.38.0 with new features:

• nstalling Docker Desktop via the PKG installer is now generally available.
• Enforcing sign-in via configuration profiles is now generally available.
• Docker Compose, Docker Scout, the Docker CLI, and Ask Gordon can now be updated independently of Docker Desktop and without a full restart (Beta).
• The new update command has been added to the Docker Desktop CLI (Mac only).
• Bake is now generally available, with support for entitlements and composable attributes.
• You can now create multi-node Kubernetes clusters in Docker Desktop.
• Ask Gordon is more widely available. It is still in Beta.

In the following steps I’m upgrading my Docker Desktop Kubernetes 1-Node Cluster to a 4-Node Kubernetes Cluster:

Go to Settings in Docker Desktop and click on Kubernetes

Click on Kind.
Here you can select the Kubernetes version and how much nodes you need.

IMPORTANT: This will create a new Kubernetes Cluster!
(the old 1-node cluster will be gone)

Creating 4-Node Kubernetes Cluster in Docker Desktop

4-Node Kubernetes Cluster running in Docker Desktop

When you have “Show System Containers” in Settings at Kubernetes on
then you see these 4-Nodes here in VSCode.

Happy Coding

 

Docker Desktop main screen

In the ever-evolving world of software development, Docker Desktop for Windows has emerged as an indispensable tool for developers. This powerful platform simplifies the process of building, sharing, and running applications within containers, offering a host of features and benefits that streamline workflows and enhance productivity. Let’s dive into what makes Docker Desktop for Windows a must-have for developers.

Easy Installation and Setup

One of the standout features of Docker Desktop for Windows is its straightforward installation process. With just a few clicks, developers can have Docker up and running on their Windows machines. The intuitive setup ensures that even those new to Docker can get started without a hitch.

Integrated GUI

Docker Desktop comes with a user-friendly Graphical User Interface (GUI) that makes managing containers, images, and settings a breeze. The GUI provides a visual representation of your Docker environment, allowing you to easily monitor and control your containers without needing to rely solely on command-line instructions.

Seamless Integration with WSL 2

For developers working with both Windows and Linux containers, Docker Desktop offers seamless integration with Windows Subsystem for Linux 2 (WSL 2). This integration allows you to switch between Linux and Windows containers effortlessly, leveraging the best of both worlds. WSL 2 provides a lightweight Linux kernel that runs alongside your Windows OS, ensuring optimal performance and compatibility.

Resource Management

Docker Desktop includes robust resource management features, enabling developers to allocate CPU, memory, and disk resources to their containers. This ensures that your development environment remains responsive and efficient, even when running multiple containers simultaneously.

Automatic Updates

Docker Desktop Automatically check for updates.

Keeping your Docker environment up-to-date is crucial for security and performance. Docker Desktop simplifies this process with automatic updates, ensuring that you always have the latest features and security patches without manual intervention.

Docker Compose Integration

Docker Compose is a powerful tool for defining and running multi-container Docker applications. Docker Desktop integrates seamlessly with Docker Compose, allowing developers to easily manage complex applications with multiple services. This integration simplifies the orchestration of containers, making it easier to develop, test, and deploy applications.

Kubernetes Support

For developers looking to dive into the world of Kubernetes, Docker Desktop offers built-in support for Kubernetes. This feature allows you to run a single-node Kubernetes cluster on your local machine, providing a convenient environment for learning and experimentation. With Kubernetes support, you can develop and test containerized applications before deploying them to a production cluster.

Volume Management

Docker Desktop Volumes management

Managing data within containers is made simple with Docker Desktop’s volume management capabilities. You can easily create, manage, and share volumes between containers, ensuring that your data persists across container restarts and updates.

Benefits for Developers

Enhanced Productivity

Docker Desktop Dev Environments

Docker Desktop streamlines the development process by providing a consistent environment across different stages of development. This consistency reduces the “it works on my machine” problem, ensuring that applications run smoothly from development to production.

Simplified Collaboration

With Docker Desktop, sharing your development environment with team members is as simple as sharing a Docker image. This ensures that everyone on your team is working with the same setup, reducing discrepancies and improving collaboration.

Flexibility and Portability

Docker containers are inherently portable, allowing you to run your applications on any system that supports Docker. This flexibility is particularly beneficial for developers working in diverse environments or deploying applications across different platforms.

Improved Security

Docker Desktop Scout

Docker Desktop provides a secure environment for running containers, isolating applications from the host system and each other. This isolation reduces the risk of security vulnerabilities and ensures that your development environment remains protected.

Conclusion

Docker Desktop for Windows is a game-changer for developers, offering a comprehensive suite of features that enhance productivity, simplify collaboration, and improve security. Whether you’re a seasoned developer or just starting with containerization, Docker Desktop provides the tools you need to build, share, and run applications with ease. Embrace the power of Docker Desktop and take your development workflow to the next level.

Here you find more information about Docker Desktop:

The Website of Docker Desktop

Docker Desktop Documentation

Skill up with Docker

Whalecome to the Docker Community

Docker in VSCode

Happy coding!

Once upon a time, in a world where technology and holiday cheer intertwined, there was a bustling community of developers eagerly awaiting the latest updates from the Microsoft Windows 11 and Windows Server Insider programs. As the festive season approached, the air was filled with excitement and anticipation.

In the heart of this community were the Microsoft MVPs (Most Valuable Professionals) and Docker Captains, who were known for their expertise and passion for technology. They decided to come together to create something truly magical for developers around the world.

One snowy evening, as the MVPs and Docker Captains gathered around a virtual fireplace, they began to brainstorm ideas. “What if we could combine the power of Windows 11, Windows Server, and Docker Containers to create a seamless development experience?” suggested one MVP, their eyes twinkling with excitement.

The idea quickly gained momentum, and soon, the group was hard at work. They envisioned a world where developers could effortlessly build, test, and deploy applications using the latest features of Windows 11 and Windows Server, all within the flexible and scalable environment of Docker Containers.

With the help of the Insider programs, they gained early access to cutting-edge features and updates. The MVPs and Docker Captains worked tirelessly, sharing their knowledge and expertise to create a series of tutorials, guides, and sample projects. These resources were designed to help developers harness the full potential of Windows 11, Windows Server, and Docker Containers.

As the holiday season progressed, the community began to see the fruits of their labor. Developers from all corners of the globe started to adopt the new tools and techniques, marveling at the ease and efficiency they brought to their workflows. The combination of Windows 11’s sleek interface, Windows Server’s robust capabilities, and Docker Containers’ flexibility created a harmonious symphony of technology.

To celebrate their success, the MVPs and Docker Captains organized a virtual holiday party. Developers joined from far and wide, sharing stories of their experiences and the innovative projects they had created. The virtual room was filled with laughter, camaraderie, and a shared sense of accomplishment.

As the night drew to a close, one of the Docker Captains raised a toast. “Here’s to the power of collaboration, the spirit of innovation, and the joy of the holiday season. May we continue to push the boundaries of technology and inspire developers everywhere.”

And so, the story of the Microsoft Windows 11 and Windows Server Insider Christmas, made possible by the dedication and expertise of the MVPs and Docker Captains, became a cherished tale in the developer community. It was a reminder that, with passion and teamwork, even the most ambitious dreams could come true.

Happy holidays, and may your coding adventures be merry and bright!

New Docker Desktop for Windows version Available

• You can now perform key operations such as starting, stopping, restarting, and checking the status of Docker Desktop directly from the command line.
• The AI Catalog in Docker Hub is directly available through Docker Desktop.

More information about this release 4.37.0 on Docker docs.

Installing new release

Enable Docker AI (Beta feature) here

Click on Apply & Restart

The New AI Docker Beta feature known as Gordon

The new AI Docker beta feature, known as “Ask Gordon,” allows you to interact with Docker’s AI assistant to get help, guidance, and answers to your Docker-related questions. Here’s how you can use it:

1. Using “Ask Gordon” in Docker CLI

• Open your terminal or command line interface.
• Use the command: docker ai.
• This will activate the “Ask Gordon” feature, and you can type your questions or commands directly.

2. Using “Ask Gordon” in Docker Desktop

• Open Docker Desktop.
• Look for the “Ask Gordon” feature, which is integrated into the interface.
• You can type your questions or requests in the provided input field.

3. Requirements

• Ensure you have an active internet connection.
• Make sure your system allows communication to https://ai-backend-service.docker.com/.

4. Enabling or Disabling “Ask Gordon”

• For Individual Users:
  • Open Docker Desktop.
  • Go to Settings > Features in development > Beta features.
  • Tick or untick the “Enable Docker AI” option.
  • Click “Apply and restart” to save changes.
• For Organizations:
  • Administrators can disable “Ask Gordon” for the entire organization using the “Cloud Settings” feature.

5. What You Can Do with “Ask Gordon”

• Ask questions about Docker commands, configurations, and best practices.
• Get help troubleshooting Docker issues.
• Learn about Docker features and updates.

Docker Public Roadmap on GitHub

 

 

Docker Desktop Software Update 4.36.0 (175267)

Use Enhanced Container Isolation

Enhancing Security with Docker Container Isolation

In today’s digital landscape, securing applications and data is paramount. Docker container isolation plays a crucial role in ensuring that applications run securely, without interference from other containers or the host system. This blog post delves into the importance of container isolation for security purposes and compares the security features of Docker’s Hyper-V engine and WSL 2 Docker engine.

The Importance of Container Isolation

Container isolation involves creating a protective boundary around each container to prevent interference between containers and the host system. This helps maintain a secure environment and avoid potential issues. Docker provides several mechanisms to enhance container isolation, including:

• Namespaces: Isolate processes, network interfaces, and file systems.
• Control Groups (cgroups): Limit and isolate resource usage (CPU, memory, disk I/O).
• Seccomp: Restrict system calls that containers can make.
• AppArmor and SELinux: Apply mandatory access control policies.

Here you find more information about AppArmor and SELinux

These mechanisms ensure that containers operate independently, reducing the risk of security breaches.

Use Docker Scout for Security vulnerability management to keep secure Container images

Enhanced Container Isolation (ECI)

Docker’s Enhanced Container Isolation (ECI) provides an additional layer of security to prevent malicious workloads from compromising Docker Desktop or the host. ECI uses advanced techniques to harden container isolation without impacting developer productivity. These techniques include:

• Running all containers unprivileged through the Linux user-namespace.
• Ensuring Docker Desktop VM immutability.
• Vetting critical system calls to prevent container escapes.
• Partially virtualizing portions of /proc and /sys inside the container.

Docker Hyper-V Engine vs. WSL 2 Docker Engine

When it comes to running Docker on Windows, users have two main options: the Hyper-V engine and the WSL 2 Docker engine. Both have their own security implications.

Docker Hyper-V Engine:

• Isolation: Hyper-V provides strong isolation by running each container in a separate virtual machine (VM). This ensures that containers are isolated from each other and the host.
• Security: Hyper-V’s dedicated kernel for Docker Desktop ensures that the integrity of kernel-level configurations is maintained. This makes it harder for malicious workloads to breach the Docker Desktop Linux VM and host.
• User Access: Docker Desktop users cannot easily access the Docker Desktop Linux VM, preventing them from modifying Docker Engine settings inside the VM.

WSL 2 Docker Engine:

• Isolation: WSL 2 uses a lightweight Linux kernel inside a Windows VM, providing a more integrated experience with the Windows operating system.
• Security: While WSL 2 offers good isolation, it shares the same instance of the Linux kernel across all WSL 2 distributions on the same Windows host. This means that Docker Desktop cannot ensure the integrity of the kernel in the Docker Desktop Linux VM, as another WSL 2 distribution could modify shared kernel settings.
• User Access: Docker Desktop users can trivially access the Docker Desktop Linux VM with the wsl -d docker-desktop command, allowing them to bypass Docker Desktop security settings.

Conclusion

Both Docker Hyper-V and WSL 2 engines offer unique advantages and trade-offs in terms of security. Hyper-V provides stronger isolation and security by running containers in separate VMs with dedicated kernels, while WSL 2 offers a more integrated and performant experience with some security limitations. Choosing the right engine depends on your specific security requirements and use cases.

Important

Before you are going to use Docker Container Isolation in production environments, always test your Docker configurations in a Test environment first and do some experience first with your own Container scenarios.

For more detailed information, you can visit the official Docker documentation.

Enhanced Container Isolation (ECI) FAQs

Exploring Docker Desktop Dev Environments (Beta)

In the ever-evolving landscape of software development, Docker has consistently been at the forefront, providing developers with tools to streamline their workflows. One of the latest additions to Docker’s suite of tools is the Docker Desktop Dev Environments (Beta). This feature promises to revolutionize the way developers collaborate and manage their development environments. Let’s dive into what makes this new feature so exciting.

What is Docker Desktop Dev Environments?

Docker Desktop Dev Environments is a feature designed to simplify the process of setting up and sharing development environments. It allows developers to create, configure, and share their development setups with ease, ensuring consistency across different machines and team members. This is particularly useful in collaborative projects where maintaining identical environments can be challenging.

Key Features

• Environment Configuration: With Docker Desktop Dev Environments, you can define your development environment using a simple configuration file. This file includes all the necessary dependencies, tools, and settings required for your project. Once defined, the environment can be easily replicated on any machine with Docker Desktop installed.
• Seamless Sharing: Sharing your development environment with team members has never been easier. Docker Desktop Dev Environments allows you to package your environment configuration and share it via a URL or a file. Team members can then import this configuration and have their environment set up in minutes.
• Consistency and Reproducibility: One of the biggest challenges in software development is ensuring that all team members are working in the same environment. Docker Desktop Dev Environments addresses this by providing a consistent setup that can be easily reproduced. This reduces the “it works on my machine” problem and ensures that everyone is on the same page.
• Integration with Docker Hub: Docker Desktop Dev Environments integrates seamlessly with Docker Hub, allowing you to store and manage your environment configurations in the cloud. This makes it easy to access and share your environments from anywhere.

Benefits for Developers

• Simplified Onboarding: New team members can get up and running quickly by importing the development environment configuration. This reduces the time spent on setting up and troubleshooting environments.
• Enhanced Collaboration: By providing a consistent environment, Docker Desktop Dev Environments fosters better collaboration among team members. Everyone works with the same tools and settings, reducing discrepancies and integration issues.
• Improved Productivity: With a standardized environment, developers can focus more on coding and less on environment setup and maintenance. This leads to increased productivity and faster development cycles.

Getting Started

To get started with Docker Desktop Dev Environments (Beta), follow these simple steps:

1. Install Docker Desktop: Ensure you have the latest version of Docker Desktop installed on your machine.
2. Create a Dev Environment: Use the Docker Desktop interface to create a new development environment. Define your environment configuration using the provided templates or create your own.
3. Share Your Environment: Once your environment is set up, share it with your team by generating a URL or exporting the configuration file.
4. Import an Environment: Team members can import the shared environment configuration and have their setup ready in minutes.

In the following steps I will Create a Dev Environment in Docker Desktop for Windows:

Click on Dev Environments and then on Get Started

Give your environment a Name, select your source and choose your IDE,
Click then on Continue

Preparing and creating.

Click on Continue

You’re all set and you can open VSCode or your IDE.

Your Dev Environment in Docker Desktop for Windows.

Your Docker Desktop for Windows Dev Environment in VSCode.

Your Dev environment microservices running in Docker Desktop

 

Conclusion

Docker Desktop Dev Environments (Beta) is a game-changer for developers looking to streamline their workflows and enhance collaboration. By providing a consistent, reproducible, and easily shareable development environment, Docker is once again proving its commitment to making developers’ lives easier. Whether you’re working on a solo project or collaborating with a large team, Docker Desktop Dev Environments is a tool worth exploring.
Here you find more information about Dev environments at Docker.

Happy coding!