Build Python3.7 images from Alpine 3.10 instead of 3.11 #1889
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.
This PR forces Lagoon to use Alpine 3.10 to build Python 3.7 images instead of 3.11
This is because Alpine 3.11 defaults to Python 3.8, and as such will install the 3.8 version of Python3-dev (and Python3.8 as well to match the dependency), resulting in version duality. First discovered in testing #1887
For a later PR should be a rework of the Python images - there is a lot of optimisation that can be done - we may not need to augment the upstream images, or may be better using a glibc-based base image (e.g. buster-slim)
Checklist
Closing issues
Put
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if such).