|
| 1 | +--- |
| 2 | +title: Deprecated and retired Docker products and features |
| 3 | +linkTitle: Deprecated products and features |
| 4 | +description: | |
| 5 | + Explore deprecated and retired Docker features, products, and open source |
| 6 | + projects, including details on transitioned tools and archived initiatives. |
| 7 | +params: |
| 8 | + sidebar: |
| 9 | + group: Products |
| 10 | +aliases: |
| 11 | +- /cloud/ |
| 12 | +- /cloud/aci-compose-features/ |
| 13 | +- /cloud/aci-container-features/ |
| 14 | +- /cloud/aci-integration/ |
| 15 | +- /cloud/ecs-architecture/ |
| 16 | +- /cloud/ecs-compose-examples/ |
| 17 | +- /cloud/ecs-compose-features/ |
| 18 | +- /cloud/ecs-integration/ |
| 19 | +- /engine/context/aci-integration/ |
| 20 | +- /engine/context/ecs-integration/ |
| 21 | +--- |
| 22 | + |
| 23 | +This document provides an overview of Docker features, products, and |
| 24 | +open-source projects that have been deprecated, retired, or transitioned. |
| 25 | + |
| 26 | +> [!NOTE] |
| 27 | +> This page does not cover deprecated and removed Docker Engine features. |
| 28 | +> For a detailed list of deprecated Docker Engine features, refer to the |
| 29 | +> [Docker Engine Deprecated Features documentation](/manuals/engine/deprecated.md). |
| 30 | +
|
| 31 | +## Products and features |
| 32 | + |
| 33 | +Support for these deprecated or retired features is no longer provided by |
| 34 | +Docker, Inc. The projects that have been transitioned to third parties continue |
| 35 | +to receive updates from their new maintainers. |
| 36 | + |
| 37 | +### Docker Machine |
| 38 | + |
| 39 | +Docker Machine was a tool for provisioning and managing Docker hosts across |
| 40 | +various platforms, including virtual machines and cloud providers. It is no |
| 41 | +longer maintained, and users are encouraged to use Docker Desktop or Docker |
| 42 | +Engine directly on supported platforms. Machine's approach to creating and |
| 43 | +configuring hosts has been superseded by more modern workflows that integrate |
| 44 | +more closely with Docker Desktop. |
| 45 | + |
| 46 | +### Docker Toolbox |
| 47 | + |
| 48 | +Docker Toolbox was used on older systems where Docker Desktop could not run. It |
| 49 | +bundled Docker Machine, Docker Engine, and Docker Compose into a single |
| 50 | +installer. Toolbox is no longer maintained and is effectively replaced by |
| 51 | +Docker Desktop on current systems. References to Docker Toolbox occasionally |
| 52 | +appear in older documentation or community tutorials, but it is not recommended |
| 53 | +for new installations. |
| 54 | + |
| 55 | +### Docker Cloud Integrations |
| 56 | + |
| 57 | +Docker previously offered integrations with multiple cloud providers to |
| 58 | +streamline container workflows. These integrations have been deprecated, and |
| 59 | +users should now rely on native cloud tools or third-party solutions to manage |
| 60 | +their workloads. The move toward platform-specific or universal orchestration |
| 61 | +tools reduced the need for specialized Docker Cloud integrations. |
| 62 | + |
| 63 | +### Docker Enterprise Edition |
| 64 | + |
| 65 | +Docker Enterprise Edition (EE) was Docker's commercial platform for deploying |
| 66 | +and managing large-scale container environments. It was acquired by Mirantis in |
| 67 | +2019, and users looking for enterprise-level functionality can now explore |
| 68 | +Mirantis Kubernetes Engine or other products offered by Mirantis. Much of the |
| 69 | +technology and features found in Docker EE have been absorbed into the Mirantis |
| 70 | +product line. |
| 71 | + |
| 72 | +### Docker Data Center and Docker Trusted Registry |
| 73 | + |
| 74 | +Docker Data Center (DDC) was an umbrella term that encompassed Docker Universal |
| 75 | +Control Plane (UCP) and Docker Trusted Registry (DTR). These components |
| 76 | +provided a full-stack solution for managing containers, security, and registry |
| 77 | +services in enterprise environments. They are now under the Mirantis portfolio |
| 78 | +following the Docker Enterprise acquisition. Users still encountering |
| 79 | +references to DDC, UCP, or DTR should refer to Mirantis's documentation for |
| 80 | +guidance on modern equivalents. |
| 81 | + |
| 82 | +### Dev Environments |
| 83 | + |
| 84 | +Dev Environments was a feature introduced in Docker Desktop that allowed |
| 85 | +developers to spin up development environments quickly. This feature is no |
| 86 | +longer under active development. Similar workflows can be achieved through |
| 87 | +Docker Compose or by creating custom configurations tailored to specific |
| 88 | +project requirements. |
| 89 | + |
| 90 | +## Open source projects |
| 91 | + |
| 92 | +Several open-source projects originally maintained by Docker have been |
| 93 | +archived, discontinued, or transitioned to other maintainers or organizations. |
| 94 | + |
| 95 | +### Registry (now CNCF Distribution) |
| 96 | + |
| 97 | +The Docker Registry served as the open-source implementation of a container |
| 98 | +image registry. It was donated to the Cloud Native Computing Foundation (CNCF) |
| 99 | +in 2019 and is maintained under the name "Distribution." It remains a |
| 100 | +cornerstone for managing and distributing container images. |
| 101 | + |
| 102 | +[CNCF Distribution](https://github.com/distribution/distribution) |
| 103 | + |
| 104 | +### Docker Compose v1 (Replaced by Compose v2) |
| 105 | + |
| 106 | +Docker Compose v1 (`docker-compose`), a Python-based tool for defining |
| 107 | +multi-container applications, has been superseded by Compose v2 (`docker |
| 108 | +compose`), which is written in Go and integrates with the Docker CLI. Compose |
| 109 | +v1 is no longer maintained, and users should migrate to Compose v2. |
| 110 | + |
| 111 | +[Compose v2 Documentation](/manuals/compose/_index.md) |
| 112 | + |
| 113 | +### InfraKit |
| 114 | + |
| 115 | +InfraKit was an open-source toolkit designed to manage declarative |
| 116 | +infrastructure and automate container deployments. It has been archived, and |
| 117 | +users are encouraged to explore tools such as Terraform for infrastructure |
| 118 | +provisioning and orchestration. |
| 119 | + |
| 120 | +[InfraKit GitHub Repository](https://github.com/docker/infrakit) |
| 121 | + |
| 122 | +### Docker Notary (now CNCF Notary) |
| 123 | + |
| 124 | +Docker Notary was a system for signing and verifying the authenticity of |
| 125 | +container content. It was donated to the CNCF in 2017 and continues to be |
| 126 | +developed as "Notary." Users seeking secure content verification should consult |
| 127 | +the CNCF Notary project. |
| 128 | + |
| 129 | +[CNCF Notary](https://github.com/notaryproject/notary) |
| 130 | + |
| 131 | +### SwarmKit |
| 132 | + |
| 133 | +SwarmKit powers Docker Swarm mode by providing orchestration for container |
| 134 | +deployments. While Swarm mode remains functional, development has slowed in |
| 135 | +favor of Kubernetes-based solutions. Individuals evaluating container |
| 136 | +orchestration options should investigate whether SwarmKit meets modern workload |
| 137 | +requirements. |
| 138 | + |
| 139 | +[SwarmKit GitHub Repository](https://github.com/docker/swarmkit) |
0 commit comments