[Bug] Wheels for Python 3.12 for musllinux missing

[sdebruyn]

Currently there is no version of this package for Alpine Linux (musslinux in Python) for Python 3.12. So after updating my azure-identity I can suddenly no longer install it in my Docker container.

[rayluo]

Currently there is no version of this package for Alpine Linux (musslinux in Python) for Python 3.12

Can you please confirm whether your "this package" means "msal" or something else? msal itself is a pure Python package thus shall work on Alpine. You may also provide some snippet such as your Dockerfile to reproduce the issue you encountered.

[sdebruyn]

It's pymsalruntime. From the moment you update msal to 1.33, an installation in an Alpine Docker image doesn't work anymore. I am using uv, but it should be the same with pip. It seems that there are no wheels published for musslinux for the pymsalpackage (only manylinux). And since the msal 1.33 requires pymsalruntime on any Linux, installation is simply not possible anymore.

[rayluo]

since the msal 1.33 requires pymsalruntime on any Linux, installation is simply not possible anymore

AFAIK, pymsalruntime remains as an optional dependency of msal. Can you show a snippet of for example the "pip install msal" failing on Alpine? My guess is your dependencies somehow include msal[broker] which requires pymsalruntime. Is that the case here?

[rayluo]

OK, I got around to it.

docker run --rm -it python:3.12-alpine pip install msal That works. So, msal itself still works fine w/ Alpine.

docker run --rm -it python:3.12-alpine pip install pymsalruntime That failed. Let me ping my PyMsalRuntime teammate @DharshanBJ to take a look.

[sdebruyn]

The tree I have is:
azure-identity -> msal-extensions -> msal[*] (so including msal[broker]) --> pymsalruntime

[rayluo]

The tree I have is: azure-identity -> msal-extensions -> msal[*] (so including msal[broker]) --> pymsalruntime

@sdebruyn , something does not add up. The msal-extensions depends on only msal, not the "msal[*]". And I can install azure-identity and/or msal-extensions inside an Alpine container too.

That said, the aforementioned issue still exists, that "pymsalruntime" cannot currently be installed on Alpine.

[DharshanBJ]

Thanks for raising this.

@rayluo @sdebruyn — musllinux is not compatible with manylinux_2_35_x86_64, as they target fundamentally different C libraries. manylinux wheels are built against glibc, while musllinux targets musl libc (used in Alpine Linux). Given this architectural difference, we currently do not plan to support pymsalruntime on Alpine/musllinux.

@rayluo To avoid issues for customers running on unsupported platforms, we should add the logic in the MSAL Python layer to only trigger the pymsalruntime flow on distros that are known to be compatible with manylinux_2_35 (i.e., glibc 2.35 or higher). I can take a work item to implement this check, so unsupported environments like Alpine won't inadvertently attempt to use this package.

For reference, here’s a list of common distributions known to support manylinux_2_35:

Ubuntu 22.04 LTS+ - glibc 2.35 - Yes
Ubuntu 24.04 LTS - glibc 2.39 - Yes
Debian 12 (Bookworm) - glibc 2.36 - Yes
Fedora 36+ - glibc 2.35 or higher - Yes
openSUSE Leap 15.5+ - glibc 2.35 or higher - Yes
Arch Linux - Rolling (glibc 2.35+ since early 2022) - Yes