Arm64 (beta) Support for Paketo Buildpacks #1387

anthonydahanne · 2024-04-04T22:20:00Z

anthonydahanne
Apr 4, 2024
Maintainer

We're looking for courageous, brave, fearless testers to have a look at beta Paketo Buildpacks Dual Arch (including ARM64)
DID YOU READ THAT RIGHT ?!
ARM64 M1/M2/M2 macbooks and AWS Graviton and Rasberry Pi processor support?

Yes
You
Did

The time has finally come! After more than 2 years patiently watching your CPU die a slow death doing some Rosetta arch. translation!
But first, test those buildpacks out, anyway you want, and let us know in comments how that works for you, your family, friends and customers!
Go to your favorite Java project - if you don't have 1, use the samples

Using pack CLI?

you replace
pack build myapp
with:
pack build -B paketobuildpacks/builder-jammy-buildpackless-tiny -b gcr.io/paketo-buildpacks/java myapp

Using Spring Boot Maven plugin?

You configure your plugin with:

       <plugin>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-maven-plugin</artifactId>
			<configuration>
				<image>
					<buildpacks>
						<buildpack>paketobuildpacks/java</buildpack>
					</buildpacks>
					<builder>paketobuildpacks/builder-jammy-buildpackless-tiny</builder>
				</image>
			</configuration>
		</plugin>

and do the usual
./mvnw clean spring-boot:build-image

Using Spring Boot Gradle Plugin?

You configure your plugin with the following in your build.gradle.kts:

tasks.bootBuildImage {
	builder.set("paketobuildpacks/builder-jammy-buildpackless-tiny")
	buildpacks.add("gcr.io/paketo-buildpacks/java")
}

or if you're feeling groovy

tasks.named("bootBuildImage") {
    builder = "paketobuildpacks/builder-jammy-buildpackless-tiny"
    buildpacks = [ "gcr.io/paketo-buildpacks/java" ]
}

and do the usual
./gradlew clean assemble bootBuildImage

But why not official / by default yet?

Well, that's a pretty big change and we don't pretend having tested all possible variations.

PLEASE 🙏 Let us know (in this thread for example) how that works for you! and the sooner we round things up, the sooner it will be default!
🚀 THANK YOU 🚀
UPDATED MAY 22: no need for beta tag anymore, it's in latest

anthonydahanne · 2024-04-05T01:14:46Z

anthonydahanne
Apr 5, 2024
Maintainer Author

And if you build native (GraalVM) based images,
* use paketobuildpacks/java-native-image:beta

update April 19th: use paketobuildpacks/java-native-image:latest
instead of paketobuildpacks/java:beta

0 replies

anthonydahanne · 2024-04-06T02:23:15Z

anthonydahanne
Apr 6, 2024
Maintainer Author

Issue reported with datadog buidlpack (<BP_DATADOG_ENABLED>true</BP_DATADOG_ENABLED>)
)

[INFO]     [creator]     ===> DETECTING
[INFO]     [creator]     7 of 15 buildpacks participating
[INFO]     [creator]     paketo-buildpacks/ca-certificates   3.7.0
[INFO]     [creator]     paketo-buildpacks/bellsoft-liberica 10.6.0
[INFO]     [creator]     paketo-buildpacks/syft              1.46.0
[INFO]     [creator]     paketo-buildpacks/executable-jar    6.9.0
[INFO]     [creator]     paketo-buildpacks/spring-boot       5.28.0
[INFO]     [creator]     paketo-buildpacks/datadog           5.8.0
[INFO]     [creator]     paketo-buildpacks/native-image      5.13.0
[...]
[INFO]     [creator]     Paketo Buildpack for Datadog 5.8.0
[INFO]     [creator]       https://github.com/paketo-buildpacks/datadog
[INFO]     [creator]       Build Configuration:
[INFO]     [creator]         $BP_DATADOG_ENABLED    true   whether to contribute the Datadog trace agent
[INFO]     [creator]       Launch Configuration:
[INFO]     [creator]         $BPL_DATADOG_DISABLED  false  whether to disable the Datadog trace agent (non native-image Java applications only!)
[INFO]     [creator]     
[INFO]     [creator]     Paketo Buildpack for Datadog 5.8.0
[INFO]     [creator]       unable to find dependency
[INFO]     [creator]       no valid dependencies for datadog-agent-java, *, and io.buildpacks.stacks.jammy.tiny in [(datadog-agent-java, 1.31.2, [io.buildpacks.stacks.bionic io.paketo.stacks.tiny *]) (datadog-agent-nodejs, 5.8.0, [io.buildpacks.stacks.bionic io.paketo.stacks.tiny *])]
[INFO]     [creator]     ERROR: failed to build: exit status 1

I don't know yet the reason of this error, it's weird cause the buildpack 5.8.0 was published multi arch , and the dependencies are not platform specific (a jar and a JS tarball)
🤔

1 reply

anthonydahanne Apr 17, 2024
Maintainer Author

problem was fixed: we didn't properly publish the Datadog multi arch buildpack

anthonydahanne · 2024-04-19T15:52:11Z

anthonydahanne
Apr 19, 2024
Maintainer Author

🚀 BIG UPDATE THIS WEEK FOR JAVA!!! 🚀

Java 22 + quaterly updates + ARM64 for:

And, java-native-image:latest is now dual arch; you can drop the beta tag (but for ARM64 builds, you still need to use a dual arch builder such as https://hub.docker.com/r/paketobuildpacks/builder-jammy-buildpackless-tiny/tags )

0 replies

anthonydahanne · 2024-06-11T03:28:17Z

anthonydahanne
Jun 11, 2024
Maintainer Author

Additional information for buildpacks that are not dual-arch supported

Only aternity and google stack driver Java buildpacks (because those agents do not have arm64 versions) are NOT dual arch supported.(thanks to @dmikusa for chasing all the remaining single arch Java buildpacks!)

If you run them on "pure" amd64 linux with a full dual arch buildpackschain (except aternity)

build

> pwd
/home/ubuntu/samples/java/maven

> cat other-bindings/aternity-bindings/type
AppInternals

> pack build test -b paketobuildpacks/bellsoft-liberica:latest  -b paketobuildpacks/syft:latest  -b paketobuildpacks/maven:latest -b paketobuildpacks/executable-jar:latest   -b paketobuildpacks/spring-boot:latest -b paketobuildpacks/aternity:latest   -B paketobuildpacks/builder-jammy-buildpackless-tiny --env SERVICE_BINDING_ROOT=/bindings  --volume $(pwd)/other-bindings:/bindings

[...]
===> DETECTING
[detector] target distro name/version labels not found, reading /etc/os-release file
[detector] paketo-buildpacks/bellsoft-liberica 10.8.0
[detector] paketo-buildpacks/syft              1.47.0
[detector] paketo-buildpacks/maven             6.17.1
[detector] paketo-buildpacks/executable-jar    6.10.0
[detector] paketo-buildpacks/spring-boot       5.30.0
[detector] paketo-buildpacks/aternity          5.4.7
[...]
[builder] Paketo Buildpack for Aternity 5.4.7
[builder]   https://github.com/paketo-buildpacks/aternity
[builder]   Aternity AppInternals Java Agent 11.8.5: Contributing to layer
[builder]     Downloading from https://pcf-instrumentation-download.steelcentral.net/riverbed-appinternals-agent-11.8.5_BL527.zip
[builder]     Verifying checksum
[builder]     Expanding to /layers/paketo-buildpacks_aternity/appinternals-java
[builder]     Writing env.launch/JAVA_TOOL_OPTIONS.append
[builder]     Writing env.launch/JAVA_TOOL_OPTIONS.delim
[builder]   Launch Helper: Contributing to layer
[builder]     Creating /layers/paketo-buildpacks_aternity/helper/exec.d/properties
[...]

runtime

> docker run --env SERVICE_BINDING_ROOT=/bindings  --volume $(pwd)/other-bindings:/bindings  -it test
[...]
Configuring Aternity AppInternals properties
Picked up JAVA_TOOL_OPTIONS: -Djava.security.properties=/layers/paketo-buildpacks_bellsoft-liberica/java-security-properties/java-security.properties -XX:+ExitOnOutOfMemoryError -agentpath:/layers/paketo-buildpacks_aternity/appinternals-java/lib/librpilj64.so -XX:MaxDirectMemorySize=10M -Xmx31491091K -XX:MaxMetaspaceSize=84608K -XX:ReservedCodeCacheSize=240M -Xss1M -XX:+UnlockDiagnosticVMOptions -XX:NativeMemoryTracking=summary -XX:+PrintNMTStatistics -Dorg.springframework.cloud.bindings.boot.enable=true
[...]

Conclusion

all good

If you run them on "pure" arm64 linux with a full dual arch chain (except aternity)

build

> pwd
/home/ubuntu/samples/java/maven

> cat other-bindings/aternity-bindings/type
AppInternals

> pack build test -b paketobuildpacks/bellsoft-liberica:latest  -b paketobuildpacks/syft:latest  -b paketobuildpacks/maven:latest -b paketobuildpacks/executable-jar:latest   -b paketobuildpacks/spring-boot:latest -b paketobuildpacks/aternity:latest   -B paketobuildpacks/builder-jammy-buildpackless-tiny --env SERVICE_BINDING_ROOT=/bindings  --volume $(pwd)/other-bindings:/bindings

[...]
===> DETECTING
[detector] target distro name/version labels not found, reading /etc/os-release file
[detector] ======== Output: paketo-buildpacks/[email protected] ========
[detector]   Build Configuration:
[detector]     $BP_EXECUTABLE_JAR_LOCATION         a glob specifying which jar files should be used
[detector]     $BP_LIVE_RELOAD_ENABLED      false  enable live process reload in the image
[detector] ======== Error: paketo-buildpacks/[email protected] ========
[detector] fork/exec /cnb/buildpacks/paketo-buildpacks_aternity/5.4.7/bin/detect: exec format error
[detector] ======== Results ========
[detector] pass: paketo-buildpacks/[email protected]
[detector] pass: paketo-buildpacks/[email protected]
[detector] pass: paketo-buildpacks/[email protected]
[detector] pass: paketo-buildpacks/[email protected]
[detector] pass: paketo-buildpacks/[email protected]
[detector] err:  paketo-buildpacks/[email protected]
[detector] ERROR: No buildpack groups passed detection.
[detector] ERROR: failed to detect: buildpack(s) failed with err
ERROR: failed to build: executing lifecycle: failed with status code: 21

conclusion

Detect won't even pass; fails at build time - the error is pretty explicit though

If you run them on Mx (silicon) macs that run on arm64 but emulate x86_64

build

> pwd
/home/ubuntu/samples/java/maven

> cat other-bindings/aternity-bindings/type
AppInternals

> pack build test -b paketobuildpacks/bellsoft-liberica:latest  -b paketobuildpacks/syft:latest  -b paketobuildpacks/maven:latest -b paketobuildpacks/executable-jar:latest   -b paketobuildpacks/spring-boot:latest -b paketobuildpacks/aternity:latest   -B paketobuildpacks/builder-jammy-buildpackless-tiny --env SERVICE_BINDING_ROOT=/bindings  --volume $(pwd)/other-bindings:/bindings

[...]
===> DETECTING
[detector] target distro name/version labels not found, reading /etc/os-release file
[detector] paketo-buildpacks/bellsoft-liberica 10.8.0
[detector] paketo-buildpacks/syft              1.47.0
[detector] paketo-buildpacks/maven             6.17.1
[detector] paketo-buildpacks/executable-jar    6.10.0
[detector] paketo-buildpacks/spring-boot       5.30.0
[detector] paketo-buildpacks/aternity          5.4.7
[...]
[builder]   BellSoft Liberica JDK 17.0.11: Contributing to layer
[builder]     Downloading from https://github.com/bell-sw/Liberica/releases/download/17.0.11+12/bellsoft-jdk17.0.11+12-linux-aarch64.tar.gz
[...]
[builder] Paketo Buildpack for Aternity 5.4.7
[builder]   https://github.com/paketo-buildpacks/aternity
[builder]   Aternity AppInternals Java Agent 11.8.5: Contributing to layer
[builder]     Downloading from https://pcf-instrumentation-download.steelcentral.net/riverbed-appinternals-agent-11.8.5_BL527.zip
[builder]     Verifying checksum
[builder]     Expanding to /layers/paketo-buildpacks_aternity/appinternals-java
[builder]     Writing env.launch/JAVA_TOOL_OPTIONS.append
[builder]     Writing env.launch/JAVA_TOOL_OPTIONS.delim
[builder]   Launch Helper: Contributing to layer
[builder]     Creating /layers/paketo-buildpacks_aternity/helper/exec.d/properties
[...]

Well, well, well 🤔 - detection passed, as well as Aternity build - even if it chose the arm64 path, since it downloaded the arm64 JVM.

We can explain that with the fact that the mac docker daemon pulled arm64 flavors for all buildpacks, except aternity since there was none, and then happily used aternity x86 compiled detect and build via Rosetta emulation.

Unfortunately, the user ends up with a franken-image that is arm64 based with an x86 agent

runtime

> docker run --env SERVICE_BINDING_ROOT=/bindings  --volume $(pwd)/other-bindings:/bindings  -it test

Configuring Aternity AppInternals properties
Picked up JAVA_TOOL_OPTIONS: -Djava.security.properties=/layers/paketo-buildpacks_bellsoft-liberica/java-security-properties/java-security.properties -XX:+ExitOnOutOfMemoryError -agentpath:/layers/paketo-buildpacks_aternity/appinternals-java/lib/librpilj64.so -XX:MaxDirectMemorySize=10M -Xmx11829091K -XX:MaxMetaspaceSize=84608K -XX:ReservedCodeCacheSize=240M -Xss1M -XX:+UnlockDiagnosticVMOptions -XX:NativeMemoryTracking=summary -XX:+PrintNMTStatistics -Dorg.springframework.cloud.bindings.boot.enable=true
Error occurred during initialization of VM
Could not find agent library /layers/paketo-buildpacks_aternity/appinternals-java/lib/librpilj64.so in absolute path, with error: /layers/paketo-buildpacks_aternity/appinternals-java/lib/librpilj64.so: cannot open shared object file: No such file or directory (Possible cause: can't load AMD 64 .so on a AARCH64 platform)

conclusion

So this is were the magic ends: the produced image is arm64 and the agent loaded an x86 .so - no can do....

Bonus Mx (silicon) macs that run on arm64 but emulate x86_64 WITH --platform (pack > 0.34.0)

build

> pack build test -b paketobuildpacks/bellsoft-liberica:latest  -b paketobuildpacks/syft:latest  -b paketobuildpacks/maven:latest -b paketobuildpacks/executable-jar:latest   -b paketobuildpacks/spring-boot:latest -b paketobuildpacks/aternity:latest   -B paketobuildpacks/builder-jammy-buildpackless-tiny --env SERVICE_BINDING_ROOT=/bindings  --volume $(pwd)/other-bindings:/bindings  --platform linux/amd64

[...]
===> DETECTING
[detector] target distro name/version labels not found, reading /etc/os-release file
[detector] paketo-buildpacks/bellsoft-liberica 10.8.0
[detector] paketo-buildpacks/syft              1.47.0
[detector] paketo-buildpacks/maven             6.17.1
[detector] paketo-buildpacks/executable-jar    6.10.0
[detector] paketo-buildpacks/spring-boot       5.30.0
[detector] paketo-buildpacks/aternity          5.4.7
[...]
[builder]   BellSoft Liberica JDK 17.0.11: Contributing to layer
[builder]     Downloading from https://github.com/bell-sw/Liberica/releases/download/17.0.11+12/bellsoft-jdk17.0.11+12-linux-amd64.tar.gz
[...]

Thanks to the --platform linux/amd64 argument, the Mac Docker daemon chose to ONLY use emulation for x86, as you can see with the JVM download (amd64)

The result image is 100% amd64 - took quite a bit longer to build though, but at least, it's fine and replicates pre dual-arch era.

runtime

docker run --env SERVICE_BINDING_ROOT=/bindings  --volume $(pwd)/other-bindings:/bindings  -it test
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
[...]
Configuring Aternity AppInternals properties
Picked up JAVA_TOOL_OPTIONS: -Djava.security.properties=/layers/paketo-buildpacks_bellsoft-liberica/java-security-properties/java-security.properties -XX:+ExitOnOutOfMemoryError -agentpath:/layers/paketo-buildpacks_aternity/appinternals-java/lib/librpilj64.so -XX:MaxDirectMemorySize=10M -Xmx11816903K -XX:MaxMetaspaceSize=84608K -XX:ReservedCodeCacheSize=240M -Xss1M -XX:+UnlockDiagnosticVMOptions -XX:NativeMemoryTracking=summary -XX:+PrintNMTStatistics -Dorg.springframework.cloud.bindings.boot.enable=true
[...]

conclusion

The image run fine, albeit a bit slower on Mac Silicon, and could be run on other x86 docker daemon (just like what we had before dual arch support)

0 replies

anthonydahanne · 2024-07-27T01:12:51Z

anthonydahanne
Jul 27, 2024
Maintainer Author

❤️ Hello arm64 fans! 🌈
A new Java composite buildpack enters the arm64 dance: https://github.com/paketo-buildpacks/java-azure/releases/tag/v12.0.0

Please try it out and let us know!

pack build test --env BP_JVM_VERSION=21 -b paketobuildpacks/java-azure:latest  -B paketobuildpacks/builder-jammy-buildpackless-tiny

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Arm64 (beta) Support for Paketo Buildpacks #1387

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 5 comments 1 reply

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Arm64 (beta) Support for Paketo Buildpacks #1387

anthonydahanne Apr 4, 2024 Maintainer

Replies: 5 comments · 1 reply

anthonydahanne Apr 5, 2024 Maintainer Author

anthonydahanne Apr 6, 2024 Maintainer Author

anthonydahanne Apr 17, 2024 Maintainer Author

anthonydahanne Apr 19, 2024 Maintainer Author

🚀 BIG UPDATE THIS WEEK FOR JAVA!!! 🚀

Java 22 + quaterly updates + ARM64 for:

anthonydahanne Jun 11, 2024 Maintainer Author

Additional information for buildpacks that are not dual-arch supported

If you run them on "pure" amd64 linux with a full dual arch buildpackschain (except aternity)

build

runtime

Conclusion

If you run them on "pure" arm64 linux with a full dual arch chain (except aternity)

build

conclusion

If you run them on Mx (silicon) macs that run on arm64 but emulate x86_64

build

runtime

conclusion

Bonus Mx (silicon) macs that run on arm64 but emulate x86_64 WITH --platform (pack > 0.34.0)

build

runtime

conclusion

anthonydahanne Jul 27, 2024 Maintainer Author

anthonydahanne
Apr 4, 2024
Maintainer

Replies: 5 comments 1 reply

anthonydahanne
Apr 5, 2024
Maintainer Author

anthonydahanne
Apr 6, 2024
Maintainer Author

anthonydahanne Apr 17, 2024
Maintainer Author

anthonydahanne
Apr 19, 2024
Maintainer Author

anthonydahanne
Jun 11, 2024
Maintainer Author

anthonydahanne
Jul 27, 2024
Maintainer Author