Skip to content

Image buildpack references without tag do not default to latest version #28921

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

Closed
dmikusa opened this issue Dec 7, 2021 · 0 comments
Closed
Assignees
Labels
type: bug A general bug
Milestone

Comments

@dmikusa
Copy link

dmikusa commented Dec 7, 2021

When building an image with ./mvnw spring-boot:build-image if I add two buildpacks to my configuration using the format to specify an image, like:

<buildpacks>
    <buildpack>gcr.io/paketo-buildpacks/bellsoft-liberica</buildpack>
    <buildpack>gcr.io/paketo-buildpacks/java-native-image</buildpack>
</buildpacks>

I get an error:

[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.5.5:build-image (default-cli) on project demo: Execution default-cli of goal org.springframework.boot:spring-boot-maven-plugin:2.5.5:build-image failed: Different digests IDs provided -> [Help 1]

Upon inspecting the output of docker images it shows that two very old versions of the first buildpack were downloaded. Ignore the 41 years ago, it's the 1.0/1.1 which are the problem. Those are the original two versions of the buildpack.

gcr.io/paketo-buildpacks/bellsoft-liberica   1.1.0      0b37a7390ca5   41 years ago   692MB
gcr.io/paketo-buildpacks/bellsoft-liberica   1.0.0      1fc7ae444343   41 years ago   681MB

It is easy enough to set a version and work around this, but the present behavior isn't what I'd say is the expected default behavior. I think fetching the "latest" version would be what's expected. This is also what the pack cli does in this situation.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Dec 7, 2021
@scottfrederick scottfrederick removed the status: waiting-for-triage An issue we've not yet triaged label Dec 7, 2021
@scottfrederick scottfrederick added this to the 2.5.x milestone Dec 7, 2021
@scottfrederick scottfrederick added the type: bug A general bug label Dec 7, 2021
@scottfrederick scottfrederick self-assigned this Dec 7, 2021
@scottfrederick scottfrederick changed the title Default to using the latest version of a buildpack image Image buildpack references without tag do not default to latest version Dec 7, 2021
@scottfrederick scottfrederick modified the milestones: 2.5.x, 2.5.8 Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

3 participants