Vanilla install fails on balenaFin

[LucianBuzzo]

I deployed this application to a balenaFin, and the app crashlooped with the following error:

30.01.21 17:04:21 (+0000)  octoprint  standard_init_linux.go:211: exec user process caused "no such file or directory"
30.01.21 17:05:26 (+0000)  octoprint  standard_init_linux.go:211: exec user process caused "no such file or directory"
30.01.21 17:05:29 (+0000) Service exited 'octoprint sha256:a2b62865f85fcfaf8cac7f39286947a727a60cf2abe9bf14de9546b96038c2d7'
30.01.21 17:06:30 (+0000) Restarting service 'octoprint sha256:a2b62865f85fcfaf8cac7f39286947a727a60cf2abe9bf14de9546b96038c2d7'
30.01.21 17:05:26 (+0000)  octoprint  standard_init_linux.go:211: exec user process caused "no such file or directory"
30.01.21 17:06:30 (+0000)  octoprint  standard_init_linux.go:211: exec user process caused "no such file or directory"

This was on balenaOS 2.58.3+rev1 with supervisor version 11.14.0

[BJClark]

I get this error as well. Did you figure out a solution?

[LucianBuzzo]

I was too excited to get going with my ender3 so I didn't investigate further. I switched to https://github.com/balenalabs-incubator/balena-octoprint which this project is forked from and that worked fine. It's possible that I have an environment variable missing or set incorrectly.

[edorgeville]

I believe the issue might be caused by this commit: https://github.com/MatthewCroughan/octobalena/commit/1dc9de81709b9496d7343d2656fb53cadb8daa5f

https://github.com/MatthewCroughan/octobalena/blob/13b5675668317ce758e67dde7b7a2ec01d7cd07d/octoprint/Dockerfile.template#L1 Being based on an alpine image, the shebang should be #/bin/sh instead of #/bin/bash. This won't break on the Raspberry Pi 3 because there is a seperate Dockerfile for it, based on debian: https://github.com/MatthewCroughan/octobalena/blob/13b5675668317ce758e67dde7b7a2ec01d7cd07d/octoprint/Dockerfile.raspberrypi3#L1

Which raises the question: why is there a seperate dockerfile specific to the Raspberry Pi 3?