Debian stable runs about five years including LTS, Ubuntu LTS gets five years of standard maintenance, and Alpine supports the main repository for about two years. Those lifetimes differ a lot, so a base image choice is also a choice about how often you must migrate.
The three lifetimes in one table
Each row uses the publisher's own page, fetched on the review date below.
| Family | Typical lifetime stated by the publisher | Release rhythm | Example current branch |
|---|---|---|---|
| Debian | Five years: three full support, two LTS | New stable roughly every two years | 13 trixie, regular end 2028-08-09 |
| Ubuntu LTS | Standard maintenance to May of the fifth year after release | LTS every two years | 24.04, May 2029 |
| Alpine | Main repository about two years | A branch each May and November | 3.24, end 2028-06-01 |
Alpine also says the community repository is supported only until the next stable branch. That is a shorter promise than the main repository, and it matters if your image installs from community.
What the difference means in practice
A long lifetime gives you fewer forced migrations. A short one keeps you closer to current software, which can also mean fewer old components in the image. Neither is better in the abstract. The cost sits in your calendar.
If a team owns forty services on Alpine, the two year lifetime means a migration wave every year or so. If those services sit on Debian, the wave is rarer but larger when it arrives, because more has changed between releases.
Turn the table into a calendar
- Export the list of base images in use from your SBOMs or image scans.
- Add each release's end of support date from the publisher page.
- Sort by date and mark everything ending within twelve months.
- Assign each marked image an owner and a target branch.
- Review the calendar every quarter, since new branches appear on a schedule.
Keep the source URL next to each date. Dates change, and a calendar without sources goes stale in silence.
Choosing with lifetime in mind
Ask three questions. How many images will share this base? How much effort does one migration cost us? Do we have the habit of rebuilding monthly or more often? A team with strong rebuild habits copes well with short lifetimes. A team that touches services once a year should prefer long ones, or pay the cost in exceptions.
Try it yourself
Click through it at your own pace, or open it full screen. Watch how findings change over time on an asset that did not change, which is the same pressure an ageing base image faces.
Where Safeguard fits
Safeguard keeps an SBOM per image and keeps scanning stored inventory as new advisories arrive, which gives you the list a lifetime calendar needs. The free scan at https://gold.safeguard.sh/scan lets you check one image first.
Quick check
Which base image family has the longest support?
By the dates in the table, Ubuntu LTS and Debian with LTS both reach about five years, while Alpine's main repository is about two. Check the current page, because dates move with each release.
Does a long support window mean I can skip rebuilds?
No. Support covers the packages, but your image only gets the fixes when you rebuild and redeploy.
Sources
Last reviewed: 19 October 2026.
