[BUG] python:3.1X-slim E: Unable to locate package libaio1

[mborovyk]

Hi community.
I'm using python:3.10-slim version of python official image on Dockerhub and recently (hour ago) after trying to build image i've got next error:
$ apt-get update && apt-get install -y --no-install-recommends libaio1
E: Unable to locate package libaio1
I hope it's fixable and i've seen that next images were updated in same time range:

• python:3.10-slim
• python:3.11-slim
• python:3.12-slim
• python:3.13-slim
  maybe even more
  https://hub.docker.com/layers/library/python/3.10-slim/images/sha256-b827cb94f814204932b4959a932fe9096643e6d5025e31465445c0302d5f9bc4

last working version for me is
python:3.10-slim@sha256:81f1cdb3770d54ecfdbddcc52c2125fce674c14a1d976dfd8f65dc0734f9c3c5

[pomaretta]

I'm using Python 3.11 base image and the system changed from Ubuntu to LinuxKit

Before:
Linux aec89c3047a5 6.14.0-1010-aws #10~24.04.1-Ubuntu SMP Fri Jul 18 20:44:30 UTC 2025 x86_64 GNU/Linux
After:
Linux a247ec3e19bc 6.10.14-linuxkit #1 SMP Thu Mar 20 16:32:56 UTC 2025 x86_64 GNU/Linux

[danbarbarito]

What a mess. Seeing a similar issue as well. Completely broke my devops pipeline

[aliir74]

We're seeing the same error in our pipelines as well :/

E: Package 'libgl1-mesa-glx' has no installation candidate

EDIT: Switching to bookworm fixed our problem.

[yosifkit]

This is caused by the images moving to the next major Debian release. To migrate, you'll need to find which package in Debian Trixie now provides what you needed from libaio1 (like libaio1t64) or stick with -bookworm images.

We only support python images on two suites of Debian at a time. As we have in the past (#633, #822) and now (#1042), we move to the newest Debian release and drop the oldest. This also means that image tags without a Debian suite qualifier (e.g., python:3 or python:3.13-slim) move to the newest release.

I'd recommend not using tags without a Debian suite qualifier (-bookworm and -trixie) since then you can control when a major OS version bump happens for you. The plain tags will change again in a few years when Debian Forky is released. We maintain python images on the two most recent releases of Debian so that users have time to migrate.

[yosifkit]

I'm using Python 3.11 base image and the system changed from Ubuntu to LinuxKit

That has nothing to do with the image. The kernel version is taken from the host (since containers all share the kernel with the host). This looks like a test run on an AWS instance and on Docker Desktop (a "linuxkit" VM in MacOS or Windows).