Support manylinux and musllinux wheels #750

Activity

1. yosifkit commented on Aug 18, 2022

   

   yosifkit

   on Aug 18, 2022

   Member

   More actions

   tk is removed on purpose in Alpine based images so that users who need it can add it back in: #484 (comment). The Alpine images are also meant to be as small as possible. With the image being currently just 48.7MB on disk, a 22MiB increase would be a significant amount.

   This variant is useful when final image size being as small as possible is your primary concern.

   - https://github.com/docker-library/docs/tree/7a85537b34a6fcef752959975c16910e38e35d03/python#pythonversion-alpine

   The debian-based slim images are smaller on purpose:

   This image does not contain the common packages contained in the default tag and only contains the minimal packages needed to run python.

   - https://github.com/docker-library/docs/tree/7a85537b34a6fcef752959975c16910e38e35d03/python#pythonversion-slim

   The "regular" images are already overly large; at 922MB, adding 148MB would still be significant. It is not really meant to have every package for every possible pip installed dependency especially for something like graphical applications. If a user needs more libraries than are provided, then they need to install them.
2. EpicWink commented on Aug 18, 2022

   

   EpicWink

   on Aug 18, 2022

   Author

   More actions

   That makes sense, although I disagree about the size concern of the full Debian image.

   What's the argument against releasing new tags?

   In any case, I think it's fine to wait to see if there's interest in the community for the Docker library Python images to support manylinux wheels. If not, this issue at least documents the missing libraries.
3. tianon commented on Aug 18, 2022

   

   tianon

   on Aug 18, 2022

   Member

   More actions

   What's the argument against releasing new tags?

   We already support a pretty obscene matrix of versions/variants (36 unique across ~9-10 unique architecture/platform combinations). 😬

   Given using X11 and OpenGL are very uncommon inside container use cases, I'm very much inclined to suggest this is working-as-designed. 🙈

   Documentation lives in https://github.com/docker-library/docs if you wanted to take a stab at documenting this better, however I don't think we should spend a lot of time/space on it (we're very limited on how much we can actually publish to the Docker Hub image description).
4. tianon

   pinned this issue on Oct 6, 2022
5. tianon

   closed this as completedon Oct 6, 2022