I’m trying to get Balena to run OpenWRT as a docker image. There is an existing Docker build for OpenWRT on a Raspberry Pi3 here: GitHub - oofnikj/docker-openwrt: OpenWrt running in Docker.
make as a pre-docker step for getting the image, which is not too bad - once you get the image, you can just keep it in the working directory of the git, and then it will automatically be uploaded to Balena when you do a balena push appname. The whole thing builds successfully locally on my MacBook (x86_64), with qemu, squashfs and fakeroot, homebrew/cask/docker and docker installed as an
armvirt-64 image. When I start it, I can expose e.g. ports 22 and 80, and then ssh into the container or use the OpenWRT Luci web interface.
I have forked the repo and added all changes that I made so it works on the Balena build hosts, and the only thing required is a 'balena push '. The forked project is here: GitHub - GeorgLippold/docker-openwrt: OpenWrt running in Docker
However, when I use it with Balena on a Raspberry Pi 3 64bit image, then it seems there is a problem with init. Init gets started, but it then terminates instantly. I get the following log messages (which according to https://pastebin.com/XiJzJbLb seems to be from init or preinit:
15.04.21 09:59:46 (+1000) openwrt Press the [f] key and hit [enter] to enter failsafe mode 15.04.21 09:59:46 (+1000) openwrt Press the , ,  or  key and hit [enter] to select the debug level 15.04.21 09:59:51 (+1000) Service exited 'openwrt sha256:84c4ee5cd2189f1fbb51a70b1e674e56ee3be3a8ebc9234b0876cef2f2861117'
I am wondering if there is a substantial difference between a “normal” docker and the docker that’s run on the RasPi 3 64bit, so that init does not work as expected?