Skip to content

Quarkus and Raspberry Pi - bare metal - blog fix #2198

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Dec 17, 2024
+2 −3
Merged

Quarkus and Raspberry Pi - bare metal - blog fix #2198

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions _posts/2024-12-09-quarkus-rpi-bare-metal.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,11 +120,10 @@ NOTE: Currently, the Dev UI is not available in the remote dev mode for security
=== Step 4 - Run in production

Of course, you can run your Quarkus app in a JVM on the target Raspberry Pi.
But the startup is a bit slow, more than ten seconds even for simple apps.
Also Raspberry Pi is not endowed with a large amount of memory.
However, Raspberry Pi is not endowed with a large amount of memory.
So what about native image?
That might be a perfect fit.
However, there's one problem - Raspberry Pi is an ARM-based single-board computer (`aarch64` architecture for Raspberry Pi 4 Model B).
There's one problem though - Raspberry Pi is an ARM-based single-board computer (`aarch64` architecture for Raspberry Pi 4 Model B).
But your machine might be Intel-based (`x86_64` architecture).
In other words, usually you cannot build the native image of your machine and run it on Raspberry Pi.

Expand Down
Loading