Pin base image to Debian Buster; update libboost version accordingly #311
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.
Drone builds (e.g. https://drone.kansalliskirjasto.fi/NatLibFi/Annif/118/1/2) were failing with error:
This (apparently) was due to that the base image
python:3.7-slim
was updated ten days ago in Docker Hub from Debian Stretch to Debian Buster, and the above 1.62.0 versions of libboost were not available to install. (Also, builds in my local machine were all the time successful for some reason.)This fixes the drone builds by updating the libboost packages to 1.67 that are available in Buster, to which the base image is also pinned (also the python version pinning is relaxed from 3.7 to 3, to allow possibly more frequent security updates).