Is there an ARM 64 version of this?

[NPSconsultingLLC]

I am trying to run this on a Pi in a docker container, but my Pi is a 64bit architecture. I've tried running the build yml, but it seems to time out after ~1 hour. I am by no means an expert here so if there is a process I should be following please feel free to point me in that direction.

[arpanghosh8453]

The build process is pretty long and needs quite a bit of Computational power. You want a docker image with arm64 compatibility?

[arpanghosh8453]

Nope, I was asking to modify the Dockerfile contents with that additional part in the right place

[NPSconsultingLLC]

I figured that out :) working on ti right now.

[NPSconsultingLLC]

Looks like it crashed out again (timed out)

[+] Building 7088.6s (23/33)                                                                             
 => => transferring context: 229B                                                                   0.0s
 => [backend-builder  1/12] FROM docker.io/library/rust:1.85-bookworm@sha256:e51d0265072d2d9d5d  2596.7s
 => => resolve docker.io/library/rust:1.85-bookworm@sha256:e51d0265072d2d9d5d320f6a44dde6b9ef13653  0.2s
 => => sha256:68726bb4bd5930eea8f798c7bec16b2f871de5b6456bfb099d043792c400a4 258.77MB / 258.77MB  108.3s
 => => sha256:1d9d474cce081e468bc6f85727459852112ba732fbbfe3236fae66c5fa8a5e 202.75MB / 202.75MB  108.3s
 => => sha256:140d15be2fea6dcd21c20cadae2601a118c08a938168718b2612ad6aca91f74a 64.36MB / 64.36MB   13.4s
 => => sha256:4378a6c11dea5043896b9425853a850807e5845b0018fe01ddee56c16245fc3c 23.54MB / 23.54MB   12.5s
 => => sha256:545aa82ec479fb0ff3a196141d43d14e5ab1bd1098048223bfd21e505b70581f 48.30MB / 48.30MB   12.5s
 => => extracting sha256:545aa82ec479fb0ff3a196141d43d14e5ab1bd1098048223bfd21e505b70581f         251.4s
 => => extracting sha256:4378a6c11dea5043896b9425853a850807e5845b0018fe01ddee56c16245fc3c         171.4s
 => => extracting sha256:140d15be2fea6dcd21c20cadae2601a118c08a938168718b2612ad6aca91f74a          91.0s
 => => extracting sha256:1d9d474cce081e468bc6f85727459852112ba732fbbfe3236fae66c5fa8a5ed5         782.2s
 => => extracting sha256:68726bb4bd5930eea8f798c7bec16b2f871de5b6456bfb099d043792c400a407        1177.7s
 => [internal] load build context                                                                   0.5s
 => => transferring context: 1.20MB                                                                 0.2s
 => [frontend-builder 1/7] FROM docker.io/library/node:20-slim@sha256:c6585df72c34172bebd8d36abe  575.2s
 => => resolve docker.io/library/node:20-slim@sha256:c6585df72c34172bebd8d36abed961e231d7d3b5cee2e  0.2s
 => => sha256:7a6ce91b8c1d5319a42f2216f1f01ef2aa9546df8ff67be5359146ef34bed80d 448B / 448B          0.2s
 => => sha256:1731fb92622470b249c590dc9989be6eaa305251fcb1a5b10ca39d4dcc1c865e 1.71MB / 1.71MB      0.7s
 => => sha256:f5334ad83891f85d8537efda275fb71a38a0ada55de771b01c808696232729e0 40.94MB / 40.94MB   64.3s
 => => sha256:9cf6a57bb448d9d8de948e9dfd590e065bb48b5625f7f3b2357c3d66b0da9385 3.31kB / 3.31kB      0.7s
 => => sha256:d3d5d8ab26d25b9040a3c2160d7ddfe3911ae81035d5b1b0904f3ebda32476b6 28.11MB / 28.11MB  108.8s
 => => extracting sha256:d3d5d8ab26d25b9040a3c2160d7ddfe3911ae81035d5b1b0904f3ebda32476b6          12.6s
 => => extracting sha256:9cf6a57bb448d9d8de948e9dfd590e065bb48b5625f7f3b2357c3d66b0da9385           0.1s
 => => extracting sha256:f5334ad83891f85d8537efda275fb71a38a0ada55de771b01c808696232729e0         219.6s
 => => extracting sha256:1731fb92622470b249c590dc9989be6eaa305251fcb1a5b10ca39d4dcc1c865e         107.1s
 => => extracting sha256:7a6ce91b8c1d5319a42f2216f1f01ef2aa9546df8ff67be5359146ef34bed80d         125.2s
 => [runtime 1/7] FROM docker.io/library/nginx:stable-bookworm@sha256:552e7481ca93ffccd046aa658d  710.8s
 => => resolve docker.io/library/nginx:stable-bookworm@sha256:552e7481ca93ffccd046aa658dbbed22caef  0.2s
 => => sha256:0fd55aefbf9bc823848558440dc31fe9789e2478ca6970308c0c28a194ed0a5c 1.21kB / 1.21kB     12.3s
 => => sha256:e1f6e1b1004a17efea5eb76046ed01b9b3c5dc51933d132469c25441fb819548 1.40kB / 1.40kB     11.9s
 => => sha256:0a62e09e5a71ee7d320a5e47a4104c245f3ea44b2ff6e73ac58da49060500bef 403B / 403B          0.4s
 => => sha256:43616d61949f51c9aec316342f158f93bea7d16a3675202243e3a45dedeccdfa 954B / 954B          0.5s
Read from remote host 10.0.1.228: Operation timed out69d0ff50554b580e48134367a 627B / 627B          0.5s
Connection to 10.0.1.228 closed.867c3ea7e2d51e876a5b5a6139e4120e53619e1dd5ec0a 40.79MB / 40.79MB    9.8s
client_loop: send disconnect: Broken pipee384f4822829cbcce20bc6b4ba32dd82a1d87 28.10MB / 28.10MB    9.5s

[arpanghosh8453]

@NPSconsultingLLC No, this means it disconnected from your PC, the last message is something you see when the ssh pipe is broken in the middle. This is not timing out.

[NPSconsultingLLC]

I can try again, but that is what I experience when it locks up ... eventually I get a broken pipe, and then I can't SSH back in (I assume its locked up)

[LachlanDev]

Hey! Just wanted to share what I did to get the latest version running on a Raspberry Pi 5 (aarch64/arm64) without waiting for the Pi to build it.

Build time was 10 mins

What I did (build on M1 Mac → transfer → run on Pi)

1) Build the image on my M1 Mac for ARM64

git clone https://github.com/arpanghosh8453/dji-logbook
cd dji-logbook

docker buildx build \
  --platform linux/arm64 \
  -t dji-logbook:pi \
  --load \
  .

2) Export the image to a compressed tarball

docker save dji-logbook:pi | gzip > dji-logbook_pi_arm64.tar.gz

3) Upload to the Pi
I uploaded dji-logbook_pi_arm64.tar.gz to the Pi

4) Load the image into Docker on the Pi
gunzip -c /home/pi/dji-logbook_pi_arm64.tar.gz | docker load

5) Run the container

docker volume create dji-data

docker run -d \
  -p 8080:80 \
  -v dji-data:/data/dji-logviewer \
  --name dji-logbook \
  dji-logbook:pi

Then I could access it at:
http://<pi-ip>:8080

Sharing / distributing ARM64 image
If it helps anyone else, I’m happy to share the dji-logbook_pi_arm64.tar.gz file I generated.

That said, is there a preferred way you’d like ARM64 images distributed going forward?

[LachlanDev]

Perfect I can do that.

[arpanghosh8453]

@NPSconsultingLLC Let me know when it's ready, I am always looking for ways to integrate, so If you have some idea how we can integrate this into the Github CI/CD pipeline, feel free to let me know.

[LachlanDev]

Started #21 a guide to setting up on Pi. I can look into some ideas to get this working via Github CI/CD pipeline.

[arpanghosh8453]

@NPSconsultingLLC @LachlanDev No issues I figured it out, future versions hopefully have it already. Check the commits on the docker.yml

[arpanghosh8453]

@NPSconsultingLLC @LachlanDev Try this out : https://github.com/arpanghosh8453/dji-logbook/pkgs/container/dji-logbook

[NPSconsultingLLC]

Hey @arpanghosh8453 , I had the same thought as @LachlanDev and I compiled the code on my Mac. Worked perfect TY Really nice work!