-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates samples for run image extension #149
Conversation
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
- When switching the run image, include the registry context (if not Docker Hub) - Verify that run image extensions are applied on top of the new run image Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Please merge #142 first and the diff will be nicer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have one nit-pick suggestion. Other than that, these are the examples we used in the KubeCon talk, and they work well.
@@ -0,0 +1,10 @@ | |||
# Buildpack API version | |||
api = "0.10" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requires #140 to update lifecycle.
Currently blocked on #140 |
…implify cowsay extension Signed-off-by: Natalie Arellano <[email protected]>
In CI a `pack build` is performed using one of libcnb's example CNBs and the upstream `cnb/sample-builder:alpine` builder, in order to test that our static MUSL compile works with non-libc base images. However, CI has just started failing with: ``` ERROR: failed to build: experimental features must be enabled when builder contains image extensions ``` (https://github.com/heroku/libcnb.rs/actions/runs/5530837180/jobs/10090742723?pr=592#step:10:107) This is due to the upstream images having been rebuilt with extension support, which is an experimental feature until the next stable Pack CLI release): buildpacks/samples#149 buildpacks/samples#142 As such until Pack CLI v0.30 is released as stable, we'll have to pin to an older `alpine` image by SHA256 ref. GUS-W-13746154.
In CI a `pack build` is performed using one of libcnb's example CNBs and the upstream `cnb/sample-builder:alpine` builder, in order to test that our static MUSL compile works with non-libc base images. However, CI has just started failing with: ``` ERROR: failed to build: experimental features must be enabled when builder contains image extensions ``` (https://github.com/heroku/libcnb.rs/actions/runs/5530837180/jobs/10090742723?pr=592#step:10:107) This is due to the upstream images having been rebuilt with extension support, which is an experimental feature until the next stable Pack CLI release): buildpacks/samples#149 buildpacks/samples#142 As such until Pack CLI v0.30 is released as stable, we'll have to pin to an older `alpine` image by SHA256 ref. GUS-W-13746154.
Signed-off-by: Natalie Arellano <[email protected]>
23ac784
to
a9f0be1
Compare
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Branching off of other branch as this is dependent on that fix