I am unable to push the code for BalenaDash to my raspberry pi

Whenever I try to push the code to my pi I always get the same reply from the terminal–

No applications found with name: balena-dash-master.

This could mean that the application does not exist, or you do
not have the permissions required to access it.

If you need help, don’t hesitate in contacting us at:

GitHub: https://github.com/balena-io/balena-cli/issues/new
Forums: https://forums.balena.io

I am running off a laptop with window 10, I am on a college campus’s wi-fi and I have tried attempting this on my home wi-fi.

Hi @jacksonpanzer,
welcome to the balena community!! Purely guessing it looks like you are using the wrong name of the application. If you go to https://dashboard.balena-cloud.com what is the name of the application there? I assume it should just be balena-dash the -master suffix is normally added when downloading a .zip from github and probably can be left off.

So I think just issusing a balena push balena-dash from with in the directory of the project should work for you.

I think I got it, when I had to put the name of the application I thought it was the folder that contained the code not the name of the application in BalenaCloud thank you.

Correction I was able to push the code but it wont display any of my stuff, it is still on the BalenaOS. I am attempting to follow this https://www.balena.io/blog/make-a-web-frame-with-raspberry-pi-in-30-minutes/ guide. I am at the step where you put “WPE_URL” in the device variables.

1 Like

Hey @jacksonpanzer, you are almost there.

Just to confirm, did you add RESIN_HOST_CONFIG_gpu_mem with the value for 396 to the FLEET configuration page?

Then on Device Variables you enter the WPE_URL.

Let me know if you get it working :wink:

Still not working, I have it set to 396 on both the fleet and individual device. I am getting these logs if this will help.

11.12.18 18:25:29 (-0600) main standard_init_linux.go:195: exec user process caused “no such file or directory”
11.12.18 18:25:32 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:25:32 (-0600) Restarting service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:25:35 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:25:39 (-0600) Restarting service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:25:39 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:25:39 (-0600) main standard_init_linux.go:195: exec user process caused “no such file or directory”
11.12.18 18:25:47 (-0600) Restarting service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:25:47 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:26:01 (-0600) Restarting service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:26:01 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:26:28 (-0600) Restarting service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:26:28 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:26:37 (-0600) Killing service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:26:37 (-0600) Killed service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:26:37 (-0600) Rebooting
11.12.18 18:27:33 (-0600) Service is already running ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:27:37 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:27:41 (-0600) Restarting service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:27:41 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:27:49 (-0600) Restarting service ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’
11.12.18 18:27:49 (-0600) Service exited ‘main sha256:ff44dbda15e2cee7ecaab4da2743f09829c72c2ec9fe9a1ea654b728bf7c5032’

I have both the fleet and the device set to 396, its still not working. I set my Device environment variables to be just like yours and it still does not work.

In the logs it keeps saying that the main service is exited and restarting over and over.

I figured it out, there was a problem while pushing the program the first time it worked after I re-pushed it.

So you got it working then?

hello, I am having the same issue:

31.12.19 19:19:11 (-0800) wpe standard_init_linux.go:207: exec user process caused “no such file or directory”
31.12.19 19:19:20 (-0800) wpe standard_init_linux.go:207: exec user process caused “no such file or directory”

I am using windows 10, I have used the video and have gotten to the same point as this person, I tried repushing the program, but no luck. any suggestions?

Hi there!
Could you confirm you are using the right application name? If you go to https://dashboard.balena-cloud.com you may confirm the right app name. Also, can you confirm you have the right keys set up in your profile?

I am having this issue as well…
wpe standard_init_linux.go:207: exec user process caused “no such file or directory”
and the Terminal window for wpe says:
‘’ SSH session disconnected
SSH reconnecting…
Spawning shell…
Error response from daemon: Container fcfcf1c639eb0e8d624b644587080ff459ebbe5af034a7e26ea865b4bbe04a88 is restarting, wait until the container is running
Error response from daemon: Container fcfcf1c639eb0e8d624b644587080ff459ebbe5af034a7e26ea865b4bbe04a88 is restarting, wait until the container is running"
Keeps doing this over and over…no URL is loaded with Launch_URL is the variable correct?

Also…scheduler says:

“06.04.20 02:35:39 (+0000) scheduler /bin/sh: /usr/src/start.sh: not found”

Hey @Aleksandr thanks for trying the project and welcome to the forum!

Just as a hunch the first thing you could try is pushing again with balena push <appname> --convert-eol. If that doesn’t help, please could you share the type of device you’re trying to use along with the OS version.

Some other things you could try:

  • Make sure you have set the device GPU memory according to the guide
  • If you’re using a Raspberry Pi 3, try the 32-bit version of the OS

If none of these make any difference come back to us with what you’ve tried and the type of device and we’ll try to deploy the same thing here and check everything works.

Hey! it is a Rasp pi 3b+. I’m not sure if it’s 32 or 64… when I downloaded the img it didn’t specify.

Hey Alex, if you open the device page on the dashboard it should tell you what version you are using under the Type heading. Did you try pushing again with balena push <appname> --convert-eol?

Holy crap that totally worked!!! Thanks SOOOO much Tmigone!! What is the “–convert-eol “ @ the end do? Eol…is that end of life? Or something? Messed with this a year ago, decide to revisit…still love this simple little project

@Aleksandr good to hear it works now : )

–convert-eol is a balena-cli flag that converts Windows style line endings to Unix formats (without changing the source code). We saw couple of users experiencing a similar issue running Windows.