Why (rpi3) is armv7 and not armv8/aarch64?

[lasote]

Why is that for rpi3?

Raspberry Pi 3	raspberrypi3	armv7hf	-

[floion]

At this moment we are not building a 64 bit OS for the PI3 Are you missing anything in particular because of this?

[lasote]

Not really, just curious. So the OS is not 64 bit. Understood. Thanks!

[lasote]

Hi again, why the resin/armv7hf-python returns this to the uname -a?

Linux ea712bd312c0 4.12.13 #1 SMP Thu Sep 14 13:00:05 UTC 2017 armv8l GNU/Linux

[floion]

It is compiled for armv8 but it's still 32 bits

[guillaumekh]

At this moment we are not building a 64 bit OS for the PI3 Are you missing anything in particular because of this?

You got a prospective customer here who does ✋ We need to run MongoDB 3.x which is 64bit-only.

[floion]

Hi, we'll revisit this and come back to you

[pesicsasa]

@guillaumekh , @floion You got a prospective customer here who does x2 (: We need to use Hyperlledger Fabric, and Hyperledger Fabric only supports 64-bit architectures. Would be a charm to use Resin for this. Please keep us updated, thanks. Sasa

[pcarranzav]

Hi @guillaumekh @pesicsasa would you contact us at solutions at resin.io to chat about this? Thanks!

[pesicsasa]

@pcarranzav please check your inbox at solutions@resin.io

[mcfilib]

@pcarranzav I'd also be interested in a 64bit ResinOS.

[benharosh]

Hi we're also facing some issues trying to run mongodb on ResinOS. MongoDB supports only 64-bit arch, while ResinOS is running the armv7l (32-bit).

[fignew]

Fedora no longer supports arm32. Only aarch64. One can no longer run Fedora containers on Balena.

[wlisac]

Also interested in 64bit balenaOS. I'd like to be able to run a 64bit version of Swift lang.

[floion]

Fixed by https://github.com/balena-os/balena-raspberrypi/pull/297

[wlisac]

@floion is there a docker hub image we can start using for this? I'm currently using balenalib/raspberrypi3-debian:stretch for 32 bit.

[floion]

@nghiant2710 have the base images been deployed?

[nghiant2710]

@floion, they're ready, just change the device-type to raspberrypi3-64 to use the armv8/aarch64 base images

[floion]

Thanks Trong. @wlisac ^

[SteeveGL]

This information is still not available in https://www.balena.io/docs/reference/base-images/base-images-ref/ ;)

[odyslam]

Hey, I am trying to use balenalib/raspberrypi3-64-ubuntu but every RUN command will produce a "standard_init_linux.go:195: exec user process caused "exec format error"

Guess it's not yet functional?

[nghiant2710]

@steevegldev, it's a bit outdated, we will update the reference soon. Thanks.

@OdysLam, where did you run that docker image? it's an aarch64 image so if you run it on a x64/x86-64 device then you will get exec format error.

[odyslam]

Hey @nghiant2710, if I understand correctly, using the base image as 64 bits is not the same as running balenaOS in 64 bits. How do I run balenaOS in 64 mode?

Because i have some already built containers which will run only on 64 ARM arch, so I suppose I need balenaOS in 64.

[nghiant2710]

@floion, can you please point @OdysLam to the raspberrypi3-64 balenaOS image? I'm not sure the images we provide here https://www.balena.io/os/ is armv7 or aarch64.

[floion]

@OdysLam we have a 64 bits OS image for Raspberry Pi3. It is under testing currently, it should be released shortly. Please stay tuned, will update this ticket once it's available.

[odyslam]

@floion thank you for your swift response. Really looking forward with this!

[wlisac]

@floion Thank you.

Just to make sure I understand this correctly: 64 bit base images are available, but it's not possible to run them with Balena until balenaOS is available in 64 bit, which is coming soon. Does that sound right? 🙂

[sgammon]

@floion any update on this? i need to run 64 bit containers, but i'm getting the error @OdysLam is getting - about exec format errors.

[odyslam]

@sgammon Apparently, the error has nothing to do with the fact that BalenaOS is 32 bits. I managed to build my containers using the --emulate command in balena-cli and loaded them on the device. Balena says that the services and containers were up and running but the services didn't seem to work.

As far as I could tell, the error had to do with the fact that I was building the images on my mac for another architecture without emulating the needed architecture. BalenaOS 32 means that the containers will be installed and all, but the services inside them will produce errors because they need 64 environment (more ram, etc.).

At least this is what I got to and I stopped looking into it until we got some news. @floion and @nghiant2710 could pitch in and verify my findings.

Cheers!

[sgammon]

Thank you for the quick reply @OdysLam

I saw your comments but I'm building via the balena push <appname> command, up to the cloud using Balena's CI services. I need 64-bit support in the container for Java gRPC which uses tcnative or conscrypt, and both only distribute 64-bit binaries.

[sgammon]

I'm curious about how to get this to work @floion @nghiant2710, or if this might be my fault in how I'm building it or what not. Thank you in advance, we're really excited about Balena on Pi

[sgammon]

Sorry @OdysLam, just to clarify, were you able to get your 64bit containers to work that way, or no? Lol

[odyslam]

Yes, I was able to build containers using the ubuntu64 for Rpi base image and ship them using the local dev mode of balena-cli. I used the --emulate command to emulate the architecture and build them on my laptop. Balena reports that containers are up and running, but I think the services inside them don't, as they expect a 64 env.

[sgammon]

i can't get it to work with any 64bit Pi image, be it alpine, ubuntu, debian, openjdk or other variants, and so on. going to keep trying

also tried the emulate flag and pushing locally but, no dice.

thank you again for your help

[SteeveGL]

64bits container require 64bits OS...

floion already answer. The image is not released yet. You have to build the yocto image yourself. But it's not easy, you have to know yocto has well or be patient.

[floion]

Hi all, we should be ready to deploy the 64 bits OS image for the pi3 today or tomorrow if nothing goes wrong. Once that is done, if you are using templated Dockerfiles then you will also be using the 64 bits base images as @nghiant2710 said above. I will let you know here when this is in production

[odyslam]

@floion these are amazing news! Can't wait to try these.

Any idea why I was able to build ubuntu64 images, use already-built images that I know for sure work in 64 env but I was able to ship them to Rpi3 and balena informed me that they worked alright?

[shaunmulligan]

@OdysLam if you pushed them through the build server, those would be be buildable on our servers because they are capable of building aarch64 as the CPU is actually an aarch64 CPU under the covers, then the supervisor would be able to download and the containers, but won't be able to run them because all of the binaries would require 64 bit CPU instruction set, which the armv7 (32 bit) variant of the RPI3 (our default) would not be able to run.

As florin said, this week we will be releasing a new device type called raspberrypi3-64, which will have the hostOS and kernel compiled to run 64 bit.

[sgammon]

thank you @floion, @shaunmulligan, and everyone else for your help, super excited!

[floion]

Hi everybody, the 64 bit variant for rpi3 is now available. Please give it a spin

[odyslam]

Hi everybody, the 64 bit variant for rpi3 is now available. Please give it a spin

@floion Excuse me for my cluelessness, but in order to run 64bit images (i.g Edgex) we need BalenaOS to be 64, am I right? thus I need to re-download BalenaOS.

[marvinroger]

@OdysLam

the supervisor would be able to download and the containers, but won't be able to run them because all of the binaries would require 64 bit CPU instruction set, which the armv7 (32 bit) variant of the RPI3 (our default) would not be able to run.

So yes, in order to run 64 bit images (without QEMU), you need the OS to be 64 bit.

[odyslam]

@marvinroger Yes I am slowly understanding how docker and balena works. Thank you everyone for this amazing work. Will make sure to upload, at some time, how Balena can be used to ship EdgeX. Still trying to set it up.

Cheers!

[sgammon]

Thank you @floion giving it a try today! :)

[sgammon]

@floion, sorry, where can i find the image? i'm assuming you mean a 64-bit host OS image, but i don't see a 64-bit Pi option on Balena.

[shaunmulligan]

@sgammon you will have to create a new application, since the rpi3-64 bit is aarch64, it can't be in an armv7 app. You can see it listed below:

[sgammon]

@shaunmulligan thank you :) that does make sense.

[sgammon]

@shaunmulligan, @floion: i'm getting issues with qemu errors trying to use the OpenJDK images (for JDK 11, JDK 8 seems to work fine). i filed a bug about it in #325 - thank you again for your work on this

[SamurAchzar]

Trying to build a Docker image here, but it's always building as 32-bit rather than 64-bit. I'm using this in my Dockerfile: FROM balenalib/raspberrypi3-64-debian:latest

Running balenaOS 2.31.5+rev5 The Host OS shows as aarch64, so do the Docker container when doing uname -a: Linux 3c555199a811 4.14.98 #1 SMP PREEMPT Mon Apr 1 15:47:35 UTC 2019 aarch64 GNU/Linux

But the files in the image are all armhf: /lib/arm-linux-gnueabihf/libm-2.24.so: ELF 32-bit LSB shared object, ARM, EABI5

[floion]

Are you using the raspberrypi3 64 bits OS image?

[SamurAchzar]

Yes.

ID="balena-os"
NAME="balenaOS"
VERSION="2.31.5+rev5"
VERSION_ID="2.31.5"
PRETTY_NAME="balenaOS 2.31.5+rev5"
MACHINE="raspberrypi3-64"
VARIANT="Development"
VARIANT_ID="dev"
RESIN_BOARD_REV="97f1273"
META_RESIN_REV="64859b0"
SLUG="raspberrypi3-64"