-
Notifications
You must be signed in to change notification settings - Fork 141
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
tf-runner-azure image broken #1020
Comments
Please feel free to try changing the version of Azure CLI here: https://github.com/weaveworks/tf-controller/blob/main/runner-azure.Dockerfile Contributions are welcome! |
Ok, I did a quick and dirty test image and it seems to work. I will do a proper Pull Request in a few days. |
I think we have a bigger issue than I thought. My quick and dirty image was made from the release 0.15.1 code and the runner images were since reworked to have a common base, which I think is good. However the common base distro is Alpine 3.18, which does not supply any other python version than 3.11, and some packages installed in the common base are python 3.11 related (py3-pip for example). This forbids the downgrading of the python version and thus blocks a proper and clean install of the Azure CLI. Also the Azure CLI has no release that support python 3.11, but it may have one soon (link to the issue tracking the progress). With all this taken into account there is two possibilities:
What do you think is best? |
We upgraded to 3.18 because many CVEs, so downgrading to 3.17 wouldn't be an option for us. |
Ok for closing as we cannot progress currently and I fully agree with your decision to keep Alpine 3.18. I will open another issue when a version of the azure-cli that officially supports python 3.11 is available. |
TF-runner image for Azure is not working
Context
I am trying to use TF-controller version 0.15.1, deployed from the Helm chart, to deploy a Storage Account on Azure as a PoC.
Expected behavior
I expected the runner to try to create the resource, and maybe fail due to authentication not being set up yet.
Observed behavior
The runner begins to process the request and do the initialization correctly, then it fails on the plan phase with the following error:
Elements that can help
I searched about this error and found that it is probably caused by the Python version used in the image (3.11) being incompatible with the Azure CLI. I also took a look at the dockerfile for the image on the master branch and the python version is not specified so I assume it is using the latest release available which means the problem is still present.
Used manifests
Terraform resource:
TF-controller chart values (basically all default besides the AWS package):
The text was updated successfully, but these errors were encountered: