Triggering a rebuild and push to docker hub should be enough:
pypa/manylinux@912b0de

The official manylinux images support PyPy, so pointing that out as well as pointing out the differences would be very useful. Something like:

Pro's:

• Updated frequently with the latest dependencies, like Pip 21.3, etc.
• Not fighting docker for image quotas, weekly stable tagged releases
• Supports manylinux 2010 like this one, but also 2014 and 2_24 as well
• Some alternate architecture support (Aarch64)

Con's:

• Only supports the latest PyPy release
• Only provides the PyPy 3.7 variant.

I'm not sure what the long term plans are for this repo, if you want to focus on the official image instead, etc - that's up to you. But adding the above information would probably help users, and could even be considered a solution to #7, for example.

https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/

https://github.com/pypa/manylinux uses https://quay.io

Right now we only support manylinux2010.

It'd be nice to support the newer version as well.

pypa/manylinux2010_x86_64 has last changed two weeks ago.

The last release of this image was two months ago.
We need to trigger a new build and push a new image.