Create "vaporio/python:*-lite" images #1
Closed
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 creates "lite" images for python which are based off of
vaporio/foundation
instead ofvaporio/buildpack-deps
. The goal for this is to be able to use the standard images as the "builder" stage, and the lite images as the "final" stage, where appropriate (see: https://github.com/vapor-ware/synse-server/blob/6eef553aa3ce4ec9bfce48d4e17a5ee259d5ca3a/dockerfile/synse.dockerfile)This should help make production images leaner,
Often, these images (both the new
*-lite
images and the previous normal images) fail to build in CI because of gpg keyserver issues, which seems like it is a fairly common problem (docker-library/official-images#4252 (comment)).I've been able to build the images locally repeatedly just fine, but not in CI. Solutions range from adding in retries to the CI build or trying a bunch of different keyservers until one succeeds, not sure which approach makes sense, but it seems like we'll want at least one of them if we want the builds to complete reliably.