Closed kworkbee closed 8 months ago
Apart from the above issue, is there any way to deal with the following error when you directly designate buildpacks
option?
ERROR: failed to initialize detector: open /cnb/buildpacks/paketo-buildpacks_adoptium/11.0.0/buildpack.toml: no such file or directory
Not the exact same symptoms, but possibly related. We had this issue come in: https://github.com/buildpacks/pack/issues/1959 and the reporter said that it looked to be caused by this Docker Mac issue https://github.com/docker/for-mac/issues/7006. Maybe worth checking out.
Other thoughts:
Just trying to narrow down what might be causing this.
@kworkbee When using Spring Boot 3.1, be sure to configure your build to use the latest Paketo builder as described in this blog post: https://spring.io/blog/2023/09/22/paketo-buildpacks-bionic-end-of-support.
You're using an ARM mac. Buildpacks don't have native support for ARM yet. In the logs I can see that it downloads the x64 version of the JDK, so there is some kind of emulation going on here (Rosetta?). Maybe that's causing the problem?
@mhalbritter
As you mentioned, The option Use Rosetta for x86/amd64 emulation on Apple Silicon
was enabled (on Docker Settings). Disabling and re-running again, it's working fine!
This is something I never thought of, and I'm glad it's solved right away! Thanks for your help!
I'll close the issue because it was caused by Docker Settings.
Expected Behavior
Originally,
bootBuildImage
task should run normally.Current Behavior
It still has been failed.
Test Environment:
Logs are below:
Possible Solution
Steps to Reproduce
bootBuildImage
taskMotivations
It affects everyone who uses the latest Spring Boot project.