Use paketobuildpacks/builder-noble-java-tiny as the default image builder

[ThomasVitale]

In #42508, the default Buildpacks builder used by the upcoming Spring Boot 3.4 has been changed to paketobuildpacks/builder-jammy-java-tiny (Ubuntu 22.04). Since the current LTS version of Ubuntu is 24.04, what do you think about using paketobuildpacks/builder-noble-java-tiny (Ubuntu 24.04) as the default instead?

[wilkinsona]

WDYT, @anthonydahanne?

[philwebb]

This has been raised again in #43960. @anthonydahanne, is there any reason we should not to upgrade in Spring Boot 3.5?

[scottfrederick]

See https://paketobuildpacks.slack.com/archives/C0124SD3GTG/p1736791693871209 for a recent Slack discussion about the stability of the Noble-based builders.

[patpatpat123]

Hello team, hello @scottfrederick , is it possible to join the slack discussion?

[scottfrederick]

@patpatpat123 There is a link here to join the Paketo Slack: https://paketo.io/community/

[mhalbritter]

Our system tests fail when using the noble tiny image, see this build scan.

ERROR: failed to launch: bash exec: no such file or directory

The tiny image contains no shell and there are no non-tiny images for noble available yet. Maybe we can rewrite the test to not need a shell.

[mhalbritter]

org.springframework.boot.image.paketo.PaketoBuilderTests#plainWarApp fail when using noble tiny image.

ERROR: failed to launch: path lookup: exec: "sh": executable file not found in $PATH

When using paketobuildpacks/builder-jammy-java-tiny:latest, this works.

[mhalbritter]

I've reverted the changes until this problem is investigated.

[mhalbritter]

The Tomcat buildpack has some special cases for the tiny images, and right now only bionic and jammy is supported. I've opened paketo-buildpacks/apache-tomcat#531. That's the reason org.springframework.boot.image.paketo.PaketoBuilderTests#plainWarApp fails.

TomEE is also affected: paketo-buildpacks/apache-tomee#309.

There's also a special case for native image, i've opened paketo-buildpacks/native-image#361 for that.

There's also special handling if no shell is available in procfile, see paketo-buildpacks/procfile#266.

[mhalbritter]

All the issues are closed, however the images aren't on DockerHub yet. There's also this PR, which AFAIK, adds the missing paketobuildpacks/builder-noble-base:latest.

[philwebb]

The PR has been merged, but I don't see images on https://hub.docker.com/r/paketobuildpacks/build-noble-base/tags yet.

[mhalbritter]

I think they have disabled the CI workflows and want to re-enable them after paketo-buildpacks/ubuntu-noble-base-images#1 is merged.