-
Notifications
You must be signed in to change notification settings - Fork 352
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
azure-cli feature installation silently fails if pipx is broken (i.e. when Python version is changed) #785
Comments
For a workaround, use a temporary copy of pipx to call
See linked issue above for details. |
Thanks for opening the issue From your log it seems like we should be able to detect when something goes wrong in the pipx installation flow
So I think a generic change here to detect problems and fail the Feature would be a good start. Perhaps we could then utilize your workaround to reinstall pipx and try again. |
I adopt this work around and it worked, but I do not understand why in Readme file got: |
When the
pipx
binary is present in the container but broken (which can be reproduced by installing a different Python version), the Azure CLI silently fails to install.Actual results:
az
command is not available.Expected results:
Repro steps:
ghcr.io/devcontainers/features/azure-cli
featureenvironment.yml
which installs a different Python version than used by the base image, for example:Docker logs
This is easier to trigger on Apple Silicon, I suspect because there's no pre-packaged azure-cli in the repo so it falls back to the pipx installation procedure.
Note that explicitly requesting the
ghcr.io/devcontainers/features/python:1
feature in the end-user's devcontainer.json (in hopes it re-runs the pipx installation sequence that was originally run during te miniconda image setup) has no effect as the install.sh checks for the presence of the pipx command, which does exist (it just doesn't execute).The text was updated successfully, but these errors were encountered: