Hello, i’ve downloaded a screenly-ose image for my balenaOS 2.65.0+rev1 on my Model 3B+ Revision: 1.3 Ram: 1 GB Sony UK. when trying to build the containers i get the following error with every container:
[Build] srly-ose-celery standard_init_linux.go:211: exec user process caused “exec format error”
[Build] Built 5 services in 0:04
[Error] Deploy failed
The command ‘/bin/sh -c pip install --no-cache-dir -r /tmp/requirements.txt’ returned a non-zero code: 1
On the screenly forum i was asked to post this here, as it seems to be a wrong -architecure-issue on balena site.
Can you please specify the image you would like to deploy? Are you following a certain tutorial or blog post? How are you deploying your code (via balenaHub, balena push, etc)?
(I’d like to understand if there is any outdated blog post or image that might cause this)
There is the Screenly OSE application in balenaHub. Have you tried this one?
Indeed, it sounds like architecture issue defined in the dockerfile. It’d be good to see the dockerfile you are using.
I tried using the “Deploy with balena” button on that repository, which builds the application in the background (without the CLI) and deploys it either a new application or as a new release to an existing application if that name already exists in your account. (You can choose after you click on the button.) I chose “Raspberry Pi3” as the device type. It built successfully for me, so perhaps you’d like to give that a try first and see if you get the same error?
Hello, thanks a lot for your help. I feel like i’ve missed the elephant in the room. I did not bother to try the non 64bit version. But it turns out that and the deploy button @alanb128 mentioned did solve the problem. Was there any way for me to know that i should not pick the 64bit version for this repo?
Hi @konni so I guess it works now, right? So what probably happened here was that you tried to run a 64bit container on a 32bit OS. You can’t do that. You can do the other way around. Meaning if you had a 64bit OS you could run 64bit containers and 32bit ones.
Hey @Konni, good to hear you got this working. A quick question back to your question : )
In your first time with the issues, any chance you remember the screenly-ose version you deployed yourself (before using DeployWithBalena button)?
I’m asking this as I saw this issue with 64-bit architecture type and it was fixed recently:
I suspect that you might tried to deploy a version without the fix and you got similar errors. Then yesterday using the Deploy with Balena button worked fine as you deployed the latest version with the fix.
Hey @mohit, can you confirm from the logs that you are seeing exec user process caused “exec format error”? Is this happening with the balena CLI push command?
When you created the app in the balena Dashboard did you select Raspberry Pi 3 or Raspberry Pi 3 (64-bit)? The 64-bit version will show a little 64 in the raspberry logo, and will say aarch64 for the Architecture.
I’m only asking because it’s common to run 32-bit apps on a 64-bit OS so I want to make sure we are aware of your app architecture type as well as your OS.
thanks for replying @klutchell when I was pushing the using balena CLI the screenly log was giving me some git branch errors and was not playing the video. it was saying asset URL null
then I followed the push method mentioned here it was then deployed successfully and git branch error was gone but video is still not being played. its again showing asset URL null.
Hey @mohit, can you try creating another app but select Raspberry Pi 3 instead? You don’t have to re-flash your device, you can just move it from the old 64-bit app to the new one.
hey @klutchell I made a new application and selected Raspberry Pi 3 and moved my device to that application.
my device(rasp pi 3b+) is running on balena OS 2.65 64bit
still video is not playing ( I setted up the GPU_mem to 192)
Do I also need to flash 32bit balena OS 2.72 ( I tried it previously but my pi was not booting up at all)
Thanks for trying out a new application build. Is it possible to try out hub.balena.io with 32bit deploy of Screenly-ose and see if 32 bit version resolves the issue for you?
