| Re: [velocitas-dev] [Velocitas] vehicle-app-cpp-template arm64 docker image build issue |
|
Thank you for the mail! We will look further into it and come back with a more detailed answer after analysis. You are also welcome to join the next Velocitas/Kuksa developer meeting (see
https://github.com/eclipse-velocitas/velocitas-docs/wiki/Developer-Meetup(s)) if you need more support or want to discuss the topic further. Med vänlig hälsning / Best regards,
From: velocitas-dev <velocitas-dev-bounces@xxxxxxxxxxx>
On Behalf Of Eduleen Talledo via velocitas-dev 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 and # FROM --platform=$TARGETPLATFORM scratch as runner Note:
·
We did not use scratch since it will still default to linux/amd64 even supplying --platform=linux/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,
|
