[velocitas-dev] [Velocitas] vehicle-app-cpp-template arm64 docker image

[Eduleen Talledo <Eduleen.Talledo@xxxxxxx>]

Hi Velocitas-dev Team,

We found a maybe a minor issue in the Dockerfile when building it for arm64 machines.

Background:

We are creating a POC using the vehicle-app-cpp-template.

Everything worked great when we built the docker images in our host machine (amd64) and deployed it in ubuntu test machine (amd64).

However, when we built the docker image for arm64 and still using our host machine (amd64) and to be deployed in our edge devices (arm64).

The final image is still in amd64.

This is how docker build the apps:

$ cd vehicle-app-cpp-template/app

$ docker build -f app/Dockerfile --progress=plain --build-arg TARGETPLATFORM=linux/arm64 -t localhost:12345/app-seat-adjuster:0.0.1 .

After building it we docker image inspect the docker image.: 

$ docker image inspect localhost:12345/app-seat-adjuster:0.0.1 | grep Arch

$ "Architecture": "amd64",

We fixed it by modifying cd vehicle-app-cpp-template/app/Dockerfile.

# FROM ghcr.io/eclipse-velocitas/devcontainer-base-images/cpp:v0.3 as builder
FROM --platform=$TARGETPLATFORM ghcr.io/eclipse-velocitas/devcontainer-base-images/cpp:v0.3 as builder

and

# FROM --platform=$TARGETPLATFORM scratch as runner
FROM --platform=$TARGETPLATFORM gcr.io/distroless/base-debian12 as runner

Note:

• We did not use scratch since it will still default to linux/amd64 even supplying --platform=linux/arm64

After this minor fix. We can now successfully deploy it with our edge devices (arm64).

Does our Dockerfile changes is correct way to go forward or do you recommend another way to build docker(arm64) images using host(amd64)?

Your response is highly appreciated.

Thank you, 

EDULEEN TALLEDO (Mr.)  Software Development Engineer  FPT Automotive -- Philippines  IT Park, Cebu City, Philippines 6000  Mobile: +63 960-2430-526 | +84 379-488-928  Email: eduleen.talledo@xxxxxxx

***********************************************************************
IMPORTANT NOTICE
This email may contain confidential and/ or privileged information that belongs to FPT Software. If you are not the intended recipient or might have received this email by accident from an unreliable source, please notify the sender from FPT Software immediately and destroy this email. Keep in mind that any unauthorized copying, editing, disclosure or distribution of the material in this email is strictly forbidden, plus against the law by which FPT Software and involved clients abide.