-
Notifications
You must be signed in to change notification settings - Fork 41.3k
Not planned
Labels
status: invalidAn issue that we don't feel is validAn issue that we don't feel is valid
Description
I'm trying to build an OCI image from a spring boot project using heroku/builder:24.
Using pack CLI, the build succeeds as follows:
➜ test git:(main) ✗ pack build test --builder heroku/builder:24
24: Pulling from heroku/builder
Digest: sha256:48dd2cc33f592cb59e55be080b20e7e0e4641e3d888686b1f9b69733dcad1dd4
Status: Image is up to date for heroku/builder:24
24: Pulling from heroku/heroku
Digest: sha256:e77197ba81c134409dedbca62c305eec6bf93f5e8b039c58ade687abe09cfc40
Status: Image is up to date for heroku/heroku:24
===> ANALYZING
Restoring data for SBOM from previous image
===> DETECTING
2 of 4 buildpacks participating
heroku/jvm 7.0.0
heroku/maven 7.0.0
===> RESTORING
Restoring metadata for "heroku/jvm:openjdk" from app image
Restoring metadata for "heroku/jvm:runtime" from app image
Restoring metadata for "heroku/maven:maven" from app image
Restoring metadata for "heroku/maven:repository" from cache
Restoring data for "heroku/jvm:openjdk" from cache
Restoring data for "heroku/maven:maven" from cache
Restoring data for "heroku/maven:repository" from cache
===> BUILDING
## Heroku OpenJDK Buildpack
However, when executing build-image task using spring-boot-maven-plugin, maven is not recognized in the detect phase as follows:
[INFO] --- spring-boot:3.4.5:build-image (default) @ test ---
[INFO] Building image 'docker.io/library/test:0.0.1-SNAPSHOT'
[INFO]
[INFO] > Pulling builder image 'docker.io/heroku/builder:24' for platform 'linux/arm64' 100%
[INFO] > Pulled builder image 'heroku/builder@sha256:48dd2cc33f592cb59e55be080b20e7e0e4641e3d888686b1f9b69733dcad1dd4'
[INFO] > Pulling run image 'docker.io/heroku/heroku:24' for platform 'linux/arm64' 100%
[INFO] > Pulled run image 'heroku/heroku@sha256:e77197ba81c134409dedbca62c305eec6bf93f5e8b039c58ade687abe09cfc40'
[INFO] > Executing lifecycle version v0.20.10
[INFO] > Using build cache volume 'pack-cache-9d8796132ca4.build'
[INFO]
[INFO] > Running creator
[INFO] [creator] Starting creator...
[INFO] [creator] Parsing inputs...
[INFO] [creator] Ensuring privileges...
[INFO] [creator] Executing command...
[INFO] [creator] ===> ANALYZING
[INFO] [creator] Timer: Analyzer started at 2025-06-12T04:32:23Z
[INFO] [creator] Image with name "docker.io/library/test:0.0.1-SNAPSHOT" not found
[INFO] [creator] Found image with identifier "e77197ba81c134409dedbca62c305eec6bf93f5e8b039c58ade687abe09cfc40"
[INFO] [creator] Timer: Analyzer ran for 34.333µs and ended at 2025-06-12T04:32:23Z
[INFO] [creator] Run image info in analyzed metadata is:
[INFO] [creator] {"Reference":"e77197ba81c134409dedbca62c305eec6bf93f5e8b039c58ade687abe09cfc40","Image":"docker.io/heroku/heroku:24","Extend":false,"target":{"os":"linux","arch":"arm64","distro":{"name":"ubuntu","version":"24.04"}}}
[INFO] [creator] ===> DETECTING
[INFO] [creator] Timer: Detector started at 2025-06-12T04:32:23Z
[INFO] [creator] Checking for match against descriptor: {linux amd64 []}
[INFO] [creator] Checking for match against descriptor: {linux arm64 []}
[INFO] [creator] Checking for match against descriptor: {linux amd64 []}
[INFO] [creator] Checking for match against descriptor: {linux arm64 []}
[INFO] [creator] ======== Results ========
[INFO] [creator] pass: heroku/jvm@7.0.0
[INFO] [creator] fail: heroku/maven@7.0.0
[INFO] [creator] Timer: Detector ran for 4.367041ms and ended at 2025-06-12T04:32:23Z
[INFO] [creator] ERROR: No buildpack groups passed detection.
[INFO] [creator] ERROR: Please check that you are running against the correct path.
[INFO] [creator] ERROR: failed to detect: no buildpacks participating
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
I'm using a Macbook Pro M2 which is arm64 arch.
Metadata
Metadata
Assignees
Labels
status: invalidAn issue that we don't feel is validAn issue that we don't feel is valid
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
wilkinsona commentedon Jun 12, 2025
This is a limitation of the builder as it only supports creating an OCI image from source. When Spring Boot's Maven plugin pushes your application's jar to the builder it doesn't find a
pom.xml
file so it fails. You'll have to usepack
or a different builder.