<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns" -->

---
title: Moving linux builds to GLIBC==2.28 | daily.dev
description: PyPy is transitioning its Linux nightly builds and upcoming releases from manylinux2014 to manylinux2_28 Docker images. This means future PyPy builds will...
canonical: https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Moving linux builds to GLIBC==2.28 | daily.dev
og:description: PyPy is transitioning its Linux nightly builds and upcoming releases from manylinux2014 to manylinux2_28 Docker images. This means future PyPy builds will...
og:url: https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns
og:image: https://api.daily.dev/og/posts/YCRRhzjnS.png
og:image:alt: Moving linux builds to GLIBC==2.28
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Moving linux builds to GLIBC==2.28

**[Planet Python](https://daily.dev/sources/planetpython)** · 1 min read · 2 upvotes · 1 comments

## Summary

PyPy is transitioning its Linux nightly builds and upcoming releases from manylinux2014 to manylinux2_28 Docker images. This means future PyPy builds will require GLIBC>=2.28, compatible with distros like AlmaLinux 8, Amazon Linux 2023, Debian 10, and Ubuntu 20.04. The change will be reflected in the next major release, PyPy 8.0.0, which is expected to include a Python 3.12 interpreter and mark the final release of the Python 3.11 interpreter.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.pypy.org/posts/2026/07/moving-linux-builds-to-glibc228.html>

## Questions this post answers

### What GLIBC version will PyPy nightly builds require after switching to manylinux2_28 images?

PyPy nightly Linux builds will require a minimum of GLIBC 2.28 once they transition from manylinux2014 to manylinux2_28 docker images. This corresponds to distributions such as AlmaLinux 8, Amazon Linux 2023, Debian 10, and Ubuntu 20.04, meaning older distros with lower GLIBC versions will no longer be supported for these builds.

_Track platform compatibility shifts like this GLIBC bump on daily.dev before they break your deployment pipeline._

### Will PyPy still release a Python 3.11 interpreter after moving to manylinux2_28 and GLIBC 2.28?

No, the next PyPy release after this GLIBC 2.28 transition will be the last one to include a Python 3.11 interpreter. That release will be versioned as PyPy 8.0.0, marking the manylinux2_28 change, and it is expected to also include a Python 3.12 interpreter.

_Developers planning Python version upgrades can follow PyPy release changes like this on daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@baz14** · 0 upvotes

> Even pypy now requires Linux no older than 5-6 years. Like a current Ubuntu LTS. It doesn't seem critical, but it's already alarming.
>
> To check `ldd --version`

## Similar posts on daily.dev

- [PyPy v7.3.21 release](https://daily.dev/posts/pypy-v7-3-21-release-yqrw9fg6h) · Planet Python · 0 upvotes · 0 comments
- [A New Python Packaging Council and Other News for May 2026 – Real Python](https://daily.dev/posts/a-new-python-packaging-council-and-other-news-for-may-2026-real-python-j4ikhcce9) · Real Python · 0 upvotes · 0 comments
- [Python 3.10.22, 3.11.17, 3.12.15, 3.13.16 and 3.14.8 are now available\!](https://daily.dev/posts/python-3-10-22-3-11-17-3-12-15-3-13-16-and-3-14-8-are-now-available--xe7htfuxa) · Python Insider · 2 upvotes · 0 comments

---

Tags: [#python](https://daily.dev/tags/python), [#linux](https://daily.dev/tags/linux)

[View this post on daily.dev](https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Moving linux builds to GLIBC==2.28","url":"https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns"},"datePublished":"2026-07-19T16:52:05.293Z","dateModified":"2026-09-14T06:25:36.668Z","description":"PyPy is transitioning its Linux nightly builds and upcoming releases from manylinux2014 to manylinux2_28 Docker images. This means future PyPy builds will...","image":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","thumbnailUrl":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","isAccessibleForFree":true,"articleSection":"Planet Python","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Planet Python","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/eac3cc584cb043b5a242d13752bd3d0c","url":"https://daily.dev/sources/planetpython"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"python,linux","timeRequired":"PT1M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Planet Python","item":"https://daily.dev/sources/planetpython"},{"@type":"ListItem","position":3,"name":"Moving linux builds to GLIBC==2.28"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns","comment":[{"@type":"Comment","text":"Even pypy now requires Linux no older than 5-6 years. Like a current Ubuntu LTS. It doesn’t seem critical, but it’s already alarming.\nTo check ldd --version","datePublished":"2026-07-20T09:26:54.939Z","dateModified":"2026-07-20T09:31:10.644Z","url":"https://daily.dev/posts/YCRRhzjnS#c-8W33uIaOT","author":{"@type":"Person","name":"Baz","url":"https://daily.dev/baz14","image":"https://lh3.googleusercontent.com/a/ACg8ocKd2iFU8YS4sV-rBJptuYSF8EHeQnm23N_dcXE1uON7_GMIlZg=s96-c"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/moving-linux-builds-to-glibc-2-28-ycrrhzjns#faq","mainEntity":[{"@type":"Question","name":"What GLIBC version will PyPy nightly builds require after switching to manylinux2_28 images?","acceptedAnswer":{"@type":"Answer","text":"PyPy nightly Linux builds will require a minimum of GLIBC 2.28 once they transition from manylinux2014 to manylinux2_28 docker images. This corresponds to distributions such as AlmaLinux 8, Amazon Linux 2023, Debian 10, and Ubuntu 20.04, meaning older distros with lower GLIBC versions will no longer be supported for these builds. Track platform compatibility shifts like this GLIBC bump on daily.dev before they break your deployment pipeline."}},{"@type":"Question","name":"Will PyPy still release a Python 3.11 interpreter after moving to manylinux2_28 and GLIBC 2.28?","acceptedAnswer":{"@type":"Answer","text":"No, the next PyPy release after this GLIBC 2.28 transition will be the last one to include a Python 3.11 interpreter. That release will be versioned as PyPy 8.0.0, marking the manylinux2_28 change, and it is expected to also include a Python 3.12 interpreter. Developers planning Python version upgrades can follow PyPy release changes like this on daily.dev."}}]}
```

