This evergreen history article uses authoritative archives and official records. Exact dates are used when documented; gradual inventions and rollouts are described as periods rather than being assigned a misleading single birthday.
Quick facts
- Docker was created inside the platform-as-a-service company dotCloud and publicly demonstrated by Solomon Hykes in March 2013.
- The project packaged Linux container technologies behind a simple image format, command-line interface and registry workflow.
- Docker images made applications easier to move consistently among laptops, test systems and production servers.
- Docker helped accelerate DevOps, microservices and the later adoption of Kubernetes.
- The company and ecosystem later focused increasingly on developer tools, Docker Desktop, BuildKit, Compose and software supply-chain security.
Origins and founding
Before Docker, Linux already had isolation technologies such as chroot, namespaces, control groups, Solaris Zones and LXC. Large internet companies used containers internally, but the tools were difficult for ordinary development teams. A developer still needed a reliable way to package an application, its dependencies and its startup instructions into one portable unit.
DotCloud, founded by Solomon Hykes, Sebastien Pahl and Kamel Founadi, operated a platform-as-a-service business. Its engineers built an internal container system to run customer applications. Hykes demonstrated that system as an open-source project at PyCon in March 2013, and the audience response convinced the company that Docker could be more important than the original hosting product.
The product takes shape
Docker provided a simple command-line workflow: build an image from a Dockerfile, run it as a container and share it through a registry. Images used layers, so common components could be reused efficiently. Docker Hub launched as a public place to distribute images, making software packaging social and repeatable.
DotCloud renamed itself Docker, Inc. in 2013 and eventually sold the original platform business. Docker Compose made multi-container development easier, while Docker Machine and Swarm addressed provisioning and orchestration. The project’s rapid growth created a new industry around container infrastructure.
Technology and major features
A container is an isolated process that shares the host operating-system kernel rather than emulating a complete machine. Namespaces separate views of processes, networks and filesystems, while control groups limit resources. A container image is an immutable package assembled from layers and described by metadata.
Docker later separated core runtime components into projects such as containerd and runc. In 2015, Docker and other companies helped create the Open Container Initiative to standardize image and runtime formats. BuildKit improved image building, and Compose became a common way to describe local application stacks.
Growth and wider influence
Docker changed the phrase “works on my machine” by making the machine environment more reproducible. Developers could run databases, queues and applications locally with commands similar to those used in continuous integration. Microservice teams deployed many small independently packaged services.
Kubernetes eventually became the dominant orchestration platform, but Docker had prepared the market by making containers understandable and popular. Even when production clusters no longer used Docker Engine directly, developers continued to build OCI-compatible images with Docker tools.
Challenges, criticism and responsibility
Containers are not automatically secure. Images can contain vulnerable libraries, secrets or malicious packages. Running privileged containers or exposing the Docker socket can compromise a host. Public images require verification, regular rebuilding and vulnerability scanning.
The ecosystem also experienced commercial tension over Docker Desktop licensing, company strategy and the difference between the Docker brand and open container standards. Teams need to understand which components are open source, which are commercial and which runtime actually operates in production.
Where it stands in 2026
By 2026, Docker remained a major developer platform rather than the only container runtime. Docker Desktop, Compose, Build Cloud, Scout and hardened images focused on fast local workflows and safer software supply chains. AI-assisted development increased demand for reproducible environments because generated code still needed dependable testing and deployment.
Docker’s future is likely to center on making complex cloud-native systems feel simple on a developer laptop. The original insight remains valid: software moves more reliably when the environment is described, versioned and built alongside the code.
Timeline
| Year | Location | Event | Why it mattered |
|---|---|---|---|
| March 2013 | Santa Clara, United States | Docker is publicly demonstrated at PyCon | Introduces a simple open-source workflow for Linux containers. |
| 2013 | San Francisco, United States | dotCloud becomes Docker, Inc. | Makes containers the company’s primary mission. |
| 2014 | Global developer community | Docker Hub and Compose-era workflows expand | Creates a shared image ecosystem and multi-container development. |
| 2015 | International cloud industry | Open Container Initiative is formed | Standardizes image and runtime formats beyond one vendor. |
| 2017–2026 | Global | containerd, BuildKit, Desktop and supply-chain tools mature | Separates standards from the developer experience and improves security. |
Frequently asked questions
Who created Docker?
Docker was created by a team at dotCloud and publicly introduced by Solomon Hykes in 2013.
Is a Docker container the same as a virtual machine?
No. A container shares the host kernel and isolates processes, while a virtual machine normally runs a complete guest operating system on virtualized hardware.
Does Kubernetes replace Docker?
Kubernetes orchestrates containers. It can run OCI containers without Docker Engine, but Docker remains widely used to build and test the images deployed to Kubernetes.
What is an OCI image?
It is a container image that follows specifications maintained by the Open Container Initiative, allowing compatibility among different tools and runtimes.
Final perspective
Docker made containers understandable, portable and easy to share. That usability changed development more than any single kernel feature. The project’s legacy is a standardized packaging culture in which infrastructure can be described as code and reproduced across teams.