Back to Devoured - November 20, 2026
DEVOURED
Docker Rebrand 2026: New Logo, Colors, and Strategy Explained

Docker Rebrand 2026: New Logo, Colors, and Strategy Explained

Design ContainerSecurity
Docker is rebranding to 'Run on Trust,' shifting its focus from simple containerization toward securing autonomous AI agents in execution environments.
What: Docker redesigned its visual identity—featuring a simplified whale symbol, violet-toned blue, and new typography—to align with its goal of providing 'trusted runtime' and 'trusted supply chain' infrastructure for AI agents and traditional apps.
Why it matters: Docker is repositioning its value proposition from portability—which is now a solved commodity—to security and governance for the unpredictable, autonomous nature of AI agents.
Deep dive
  • Strategic Pivot: Transitioning from just 'Build, Ship, Run' to 'Run on Trust' with a focus on containment for AI.
  • Visual Overhaul: New 'Docker Base' color (#6172FF), GT Planar typography, and a simplified whale logo.
  • New Product Direction: Development of Docker Sandboxes (SBX) specifically for isolating and controlling AI agent execution.
  • Security Focus: Emphasis on supply-chain security and hardened images for autonomous workflows.
Decoder
  • Autonomous AI agent: A program capable of completing complex tasks by planning, using tools, and making decisions without human intervention.
  • Trusted runtime: An execution environment designed to prevent malicious or unauthorized code from accessing host system resources.
Original article

New Docker. New whale. New mission. 🐳

On November 19, 2026, Docker introduced its new brand identity, including a redesigned logo, a new color palette, and a bigger strategic ambition.

The message? Run on Trust.

As a Docker Captain and container security author, I have a few thoughts. And some book announcements of my own!

1. Docker's Angle: From Containers to Containment

Docker became famous for making applications portable and reproducible. Now, with autonomous AI agents entering development workflows, Docker is positioning itself as the trusted execution layer for both applications and agents.

We need to containerize the application and contain the agent.

What changed?

Old Docker New Docker (2026)
Logo Whale carrying containers Simplified whale and containment symbol
Signature color Docker Blue #2496ED Base Blue #6172FF
Core message Build, Ship, Run Run on Trust
Main focus Containerization Trusted execution and containment
Workloads Applications and services Applications and autonomous AI agents
Audience Primarily developers Developers, enterprises, and AI builders
Security story Container and supply-chain security Trusted runtime, supply chain, and ecosystem

Docker isn't abandoning containers. It's extending the principles that made containers successful into the AI era. Its commitment to containers, open source, and developers continues.

The new Docker colors

The familiar bright blue gets a more violet-toned replacement, supported by neutral backgrounds and vivid accents.

Primary palette

Color Hex
Base #6172FF
Canvas #F5F2EE
Zero #FFFDFA
Ether #101010
Ink #1D1D1D

Secondary palette

Color Hex
Launch #FF6A3D
Sand #FFCEA5
Neutral #DDD4C9
Air #D1E4FF
Bloom #F3E5F6
Flux #00E476
Trigger #FF3D40
Console #3345D6
Root #5C0909

Typography changes too, with GT Planar as the primary typeface and GT Standard Mono for technical accents.

New words, new priorities

Docker's new messaging centers on three pillars:

  1. Trusted Runtime: Isolate and run autonomous agents safely.
  2. Trusted Supply Chain: Protect the software and dependencies those agents use.
  3. Trusted Ecosystem: Bring tools, models, and security controls together.

Two phrases capture the direction particularly well:

Trust Docker for the agents you don't.

Contain your agents, not your ambition.

This is an interesting shift. Containers made software portable. Docker Sandboxes aim to make autonomous execution controllable, with Docker AI Governance alongside them to help teams govern agent activity.

And the whale? He's still here.

Back in October 2013, Docker's community named its whale Moby Dock, a playful reference to Herman Melville's 1851 novel Moby-Dick. Captain Ahab spent that story hunting a whale.

Thirteen years later, Docker's whale has evolved again. Sorry, Captain Ahab. But don't worry: Captain Ahab is still around, too. He's a character in my comic book Black Forest Commandos: Asgard Mission.

2. My Angle: New Docker, New Books

As a Docker Captain, I've spent years helping developers secure their containers, supply chains, and Kubernetes environments.

Docker's new direction fits what I've been working on throughout 2026: Security for both containers and autonomous agents.

And I have three books to talk about.

Book Status What's changing?
Black Forest Shadow 2.0 Released November 13, 2026 194 full-color pages, three new DLCs, updated security lessons
Docker Sandboxes (SBX) In development A standalone, hands-on guide to isolating AI agents
Docker and Kubernetes Security 2.0 Planned for early 2027 A substantive second edition with refreshed branding and security content

Black Forest Shadow 2.0: The Shadow Returns 🌲

On Friday the 13th of November, I released the second edition of Black Forest Shadow, my dark fantasy guide to Docker and Kubernetes security.

The new edition expands from 143 to 194 pages, adds three bonus stories, upgrades the illustrations to full color, and updates the technical lessons with Docker Sandboxes, SIP (Security Immediate Plan), and recent supply-chain attacks.

Even in the Black Forest of 1865, security threats keep evolving.

Docker Sandboxes: Contain, Don't Just Containerize 📦

My next book focuses entirely on Docker Sandboxes (sbx).

I'll cover agent isolation, sandbox architecture, networking, credentials, Kits, reproducible development environments, and the trade-offs between containers and sandboxes.

The fun part? I'm using Docker Sandboxes as the development environment to build the book itself.

Docker and Kubernetes Security 2.0 🐳

Finally, I'm announcing the upcoming second edition of Docker and Kubernetes Security, planned for early 2027.

The first edition covered the security lifecycle from container images to Kubernetes runtime protection. The second edition will revisit that foundation in light of evolving supply-chain attacks, hardened images, attestations, and autonomous development workflows.

It will also feature a redesigned cover aligned with Docker's new identity.

Not merely a new logo on an old book. A proper second edition.

Docker is changing how it presents itself to the world, and I'm excited to see where its focus on trusted execution leads.

One thing hasn't changed: Secure software still needs boundaries, evidence, and practical controls.

Contain your agent, containerize your application, and drink good coffee while you do it (I recommend beans from Ethiopia):

Run on Trust.

Explore all 56 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi