Installing Screenly OSE


#1

Hi guys,
Has anyone had any success installing Screely-OSE onto a Pi via Resin?
I’ve gotten as far as the installation process, but in the device logs, all i’m getting is the following.
"Failed to start application ‘registry.resin.io/essencescreenly/ccd9b46258df13f0e500974d4d5163fb6aaa6b17’ due to ‘Application architecture incompatible with raspberry-pi2: exec format error’ "

Its the RPi2 software being installed onto a RPi2, so im not really sure what the issue could been.
Any advice is appreciated.
Thanks
Paul


#2

Hi Paul,

Looks like you pushed an image with

FROM debian:jessie

which is an x86_64 image. Which is why you are seeing this error.


#3

Hi Lifeeth,
Thanks for the insight.
Any suggestions as to how I remedy this? Im not really sure about how to get other versions. i pulled that from screenly’s own repo.


#4

You can fork the repo and change the base image to rpi-raspbian -> Following https://docs.resin.io/runtime/resin-base-images/


#5

Hi @paulcarass I’m guessing you are trying to install from this repo? https://github.com/wireload/screenly-ose

The base images mentioned above should mean switching in the Dockerfile from FROM debian:jessie to FROM resin/raspberrypi2-debian:jessie, as mentioned above. But to generally migrate this onto a resin.io device, a few more changes are required. Had some time tonight, and took a shot at it. Needed to:

  • add some more dependencies
  • change config to store persistent data on the /data partition
  • change port to 80 for the control interface and set an option to be only reached through the Device Public URL (for remote managament) (this is probably something that not everyone wants to do, so it’s optional)

… and maybe a couple of other small things.

I haven’t had a screen at hand to try that out, but the backend seems to work at least, so could give it a try if interested. No guarantees, though!

Should also work with other Raspberry Pi versions too (not just RPi2).


#6

Hi Gergely,
Thanks for the advice and help. Im quite new to coding and github. i could fork the screenly repo, but making those changes would have taken me a very long time! haha
This seems like a great solution for me for what I’m looking to do, manage 30+ digital signage screens, so I would definitely take on a paid account with resin if I can get it working as I like.

This did indeed install to my pie with no issues. And i can access the Public IP for it, so I can upload content and manage the device, but I’m not getting any output to my monitor for it.
Any suggestions what could be causing that?
Paul


#7

Hi Paul,

I looked into the Dockerfile further and also screenly-ose installation procedure. Looks like the Dockerfile does not run the screen components at all - It seems to be designed only for development of the management console. You will have to copy things from the screenly-ose raspbian installation script ( https://www.screenly.io/install-ose.sh ) into a fresh Dockerfile and push to your application.


#8

ah, @lifeeth thanks for that, should have properly tested it before saying anything… Had some better ideas as well since then how to deploy this better as well, but looks like some more reverse-engineering is needed (so it’s definitely not an overnight project)

@paulcarass if you are looking to manage digital signage screens, maybe would recommend you to take a look at:

and the blogpost that goes with it:


#9

Hi @paulcarass – if I may ask a silly question – why is the combination of resin and screenly open source better for your use case than the commercial edition of screenly? I am not trying to extract a specific answer, I really have no idea.