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: Jul 24, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
29 Nov 10, 2025No29.6.2Active
28 Feb 20, 2025May 13, 202672d ago28.5.2EOL
27 Jun 25, 2024May 3, 2025447d ago27.5.1EOL
26.1 Apr 22, 2024Feb 17, 2025522d ago26.1.5EOL
26.0 Mar 20, 2024Jun 8, 2024776d ago26.0.2EOL
25.0 Jan 19, 2024Dec 4, 2026in 133d25.0.16Active
24.0 May 16, 2023Jun 8, 2024776d ago24.0.9EOL
23.0 Feb 2, 2023May 19, 2025431d ago23.0.18EOL
20.10 Dec 9, 2020Dec 10, 2023957d ago20.10.27EOL
19.03 Jul 22, 2019Jan 8, 20212023d ago19.03.15EOL
18.09 Nov 8, 2018Aug 22, 20192528d ago18.09.9EOL
18.06 Jul 18, 2018Dec 8, 20182785d ago18.06.3EOL
18.05 Apr 25, 2018Aug 18, 20182897d ago18.05.0EOL
18.04 Mar 27, 2018Jun 9, 20182967d ago18.04.0EOL
18.03 Mar 14, 2018May 10, 20182997d ago18.03.1EOL
18.02 Jan 26, 2018Apr 21, 20183016d ago18.02.0EOL
17.12 Dec 15, 2017Feb 10, 20183086d ago17.12.1EOL
18.01 Dec 12, 2017Mar 7, 20183061d ago18.01.0EOL
17.11 Nov 17, 2017Jan 27, 20183100d ago17.11.0EOL
17.10 Oct 13, 2017Dec 20, 20173138d ago17.10.0EOL
17.09 Sep 22, 2017Nov 17, 20173171d ago17.09.1EOL
17.07 Aug 28, 2017Oct 26, 20173193d ago17.07.0EOL
17.06 Jun 20, 2017Sep 29, 20173220d ago17.06.2EOL
17.05 May 4, 2017Jul 28, 20173283d ago17.05.0EOL
17.04 Apr 3, 2017Jun 4, 20173337d ago17.04.0EOL
17.03 Feb 23, 2017May 5, 20173367d ago17.03.2EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions