Skip to content
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

Add history when adding buildpack or extension layers #1099

Merged
merged 15 commits into from
May 30, 2023
Merged

Conversation

natalieparellano
Copy link
Member

@natalieparellano natalieparellano commented May 22, 2023

Fixes #411

dive on an image built using this lifecycle:
Screenshot 2023-05-23 at 10 28 52 AM

The first 3 layers are from the base image.

exporter.go Outdated Show resolved Hide resolved
@natalieparellano natalieparellano added this to the lifecycle 0.17.0 milestone May 22, 2023
Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
…ssage

Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
We need to add to the launch cache when adding layers so that the next build will be faster

Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
The digest for a remote image from imgutil
should match the digest for a remote image from ggcr
unless the user specifically requested modifications like overriding history

Signed-off-by: Natalie Arellano <narellano@vmware.com>
@jabrown85
Copy link
Contributor

@natalieparellano does the history from the base image make it into the final image if present?

Copy link
Contributor

@jabrown85 jabrown85 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is super cool to see! Commented but no concern from me.

layers/factory.go Show resolved Hide resolved
const (
BuildpackLayerName = "Layer: '%s', Created by buildpack: %s"
ExtensionLayerName = "Layer: '%s', Created by extension: %s"
LauncherConfigLayerName = "Buildpacks Launcher Config"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be named a little more generic given the layer name?

Suggested change
LauncherConfigLayerName = "Buildpacks Launcher Config"
LauncherConfigLayerName = "Buildpacks Config"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left as-is for now because https://github.com/buildpacks/rfcs/blob/main/text/0102-history.md has "launcher", but we can change it if anyone has a strong opinion

Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
Signed-off-by: Natalie Arellano <narellano@vmware.com>
@natalieparellano natalieparellano mentioned this pull request May 30, 2023
10 tasks
imgutil mutates the image (history) for newer platforms, so the SHA is different

Signed-off-by: Natalie Arellano <narellano@vmware.com>
@natalieparellano natalieparellano marked this pull request as ready for review May 30, 2023 17:09
@natalieparellano natalieparellano requested a review from a team as a code owner May 30, 2023 17:09
Signed-off-by: Natalie Arellano <narellano@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[RFC #0102] Image history metadata
2 participants