Update what packages we install in our "release" and "latest" images #3633
Assignees
Comments
SeanTAllen
added a commit
that referenced
this issue
Sep 5, 2020
Previously it was based on glibc which might not be the same as the base image that we are using. Closes #3633
SeanTAllen
added a commit
that referenced
this issue
Sep 7, 2020
Previously it was based on glibc which might not be the same as the base image that we are using. The PR job to test that this image builds is turned off my this commit as it won't build til after the next release. An issue has been created to turn it back on after the next release. Closes #3633
SeanTAllen
added a commit
that referenced
this issue
Sep 8, 2020
Previously it was based on glibc which might not be the same as the base image that we are using. The PR job to test that this image builds is turned off my this commit as it won't build til after the next release. An issue has been created to turn it back on after the next release. Closes #3633
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, we use the generic glibc build which means that the builder environment and the docker image base for release and latest need to match.
Once #3632 is done, we will have explicit nightly and release images for ubuntu 20.04.
We should switch release and latest to doing
ponyup platform ubuntu20.04to make sure they install the matching release.Further,
we need to update the logic in
handle-external-event.ymlto trigger build those images not when the generic glibc package is available in cloudsmith but when the ubuntu20.04 packages are.The text was updated successfully, but these errors were encountered: