-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
common-utils Azure linux 3 support #1283
Comments
Hello @OneQi-MS , Thank you for opening this issue. Would you kindly provide the detailed error message to check this further. Also if possible kindly provide the devcontainer.json (basically a minimum reproducible example) for this. With Regards, |
This is the only error message I got from creation log. My devcontainer file is under microsoft emu account so I probably can't share it. But it's a simple one. You can reproduce it with this image: |
Hi @OneQi-MS , Thank you for the details. Unfortunately as per what I saw from the image reference you shared, this specific distro doesn’t seem to support any of apt, apk, microdnf, dnf or yum package managers. It appears to support rpm alone for the moment. Currently the common-utils feature doesn't support installation using rpm. Also changing it to support rpm would require major changes as package dependency management would have to be taken care of explicitly unlike above mentioned package managers. Also as you would already be knowing that common-utils supports cbl-mariner 2.0. So if that could still be used, it could be the best possible approach for the moment. With Regards, |
Azure linux 3 can use dnf and tdnf to do package management. |
Hi,
AzureLinux 3 change the ID to AzureLInux instead of mariner.
Common-utils doesn't work on AzureLinux 3 image. Is there any plan to support it?
Linux distro azurelinux not supported.
ERROR: Feature "Common Utilities" (ghcr.io/devcontainers/features/common-utils) failed to install! Look at the documentation at ********/devcontainers/features/tree/main/src/common-utils for help troubleshooting this error.2025-02-28 20:30:32.284Z:
The text was updated successfully, but these errors were encountered: