Feature: More robust Python version mismatch handling #662
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The basis of my work in this PR was trying to use this custom base image: docker.io/huanjason/scikit-learn:latest. When using that base image, our attempt at installing the requested python version will fail. In that situation, I believe it makes sense to report it to the user and fallback to the system's default python version. The alternative is failing completely and effectively giving up on running that base image.
I also included a bit of work to make it possible to use arm runners locally. This just makes local development easier as we use the same architecture for the worker and runner. Without this change, for images with an arm version available, the worker will pull that version and it will not run.
Below is an example application with the custom base image mentioned above: