Docker Engine End of Life Dates

other

Developers rely on Docker Engine to streamline application deployment and management, and its widespread adoption is a testament to its effectiveness in solving complex containerization challenges. Created to simplify the process of deploying applications in containers, Docker Engine has been maintained by Docker Inc since its inception. The reason developers use Docker Engine is its ability to provide a consistent and reliable way to package, ship, and run applications, making it an essential tool in modern software development. With a history of continuous improvement, Docker Engine has become a staple in the development community, with its first release dating back to 2013.

The end-of-life landscape for Docker Engine is characterized by a large number of versions that have reached the end of their support cycle, with 24 out of 26 total versions no longer receiving updates or security patches. Currently, there are only 2 active versions of Docker Engine, with the latest stable version being 29.5.3. The most recent version to reach end-of-life was version 28, which occurred on 2026-05-13. Notably, there is no next scheduled end-of-life date announced for any of the remaining active versions, providing developers with a window of opportunity to plan their upgrades without imminent deadlines.

The security picture for Docker Engine is remarkably clear, with no known Common Vulnerabilities and Exposures (CVEs) tracked, and consequently, no critical CVEs. This indicates a high level of security maturity and a strong focus on vulnerability management by the maintainers. As a result, the most affected version is not applicable, given the absence of any CVEs. With no known vulnerabilities, Docker Engine is considered a secure choice for developers. To maintain the security and integrity of their applications, developers should continue to monitor the Docker Engine versions they use and plan to upgrade to newer versions as they become available, ensuring they stay within the supported lifecycle and benefit from ongoing security patches and updates.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
29 Nov 10, 2025—No—29.9.2—Active
28 Feb 20, 2025—May 13, 2026163d ago28.5.2—EOL
27 Jun 25, 2024—May 3, 2025538d ago27.5.1—EOL
26.1 Apr 22, 2024—Feb 17, 2025613d ago26.1.5—EOL
26.0 Mar 20, 2024—Jun 8, 2024867d ago26.0.2—EOL
25.0 Jan 19, 2024—Dec 4, 2026in 42d25.0.18—EOL soon
24.0 May 16, 2023—Jun 8, 2024867d ago24.0.9—EOL
23.0 Feb 2, 2023—May 19, 2025522d ago23.0.18—EOL
20.10 Dec 9, 2020—Dec 10, 20231048d ago20.10.27—EOL
19.03 Jul 22, 2019—Jan 8, 20212114d ago19.03.15—EOL
18.09 Nov 8, 2018—Aug 22, 20192619d ago18.09.9—EOL
18.06 Jul 18, 2018—Dec 8, 20182876d ago18.06.3—EOL
18.05 Apr 25, 2018—Aug 18, 20182988d ago18.05.0—EOL
18.04 Mar 27, 2018—Jun 9, 20183058d ago18.04.0—EOL
18.03 Mar 14, 2018—May 10, 20183088d ago18.03.1—EOL
18.02 Jan 26, 2018—Apr 21, 20183107d ago18.02.0—EOL
17.12 Dec 15, 2017—Feb 10, 20183177d ago17.12.1—EOL
18.01 Dec 12, 2017—Mar 7, 20183152d ago18.01.0—EOL
17.11 Nov 17, 2017—Jan 27, 20183191d ago17.11.0—EOL
17.10 Oct 13, 2017—Dec 20, 20173229d ago17.10.0—EOL
17.09 Sep 22, 2017—Nov 17, 20173262d ago17.09.1—EOL
17.07 Aug 28, 2017—Oct 26, 20173284d ago17.07.0—EOL
17.06 Jun 20, 2017—Sep 29, 20173311d ago17.06.2—EOL
17.05 May 4, 2017—Jul 28, 20173374d ago17.05.0—EOL
17.04 Apr 3, 2017—Jun 4, 20173428d ago17.04.0—EOL
17.03 Feb 23, 2017—May 5, 20173458d ago17.03.2—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions