Dockerfile: Fix python installation process on latest alpine #132
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 Dockerfile build has been failing for like a month and a half, and I honestly just didn't bother to look into why until today, since there weren't any balance changes to speak of (that I cared about). Turns out, the way the Dockerfile was linking up python just doesn't work anymore on latest alpine. So now it just uses the system
py3-pip
package to install pip and a python virtual environment for the bloodytools dependencies themselves.Maybe related: Should there just be a task in the nightly CD workflow that just runs a
docker build .
to catch integration issues like this?