in a digital-signage project, we do for a customer, we are using balenaCloud. First of all, it works for almost everything like a charm. We use balenaOS as the host-system on RaspberryPi’s and IntelNuc’s to show images from AWS S3 with a modified Electron-App on the connected displays. BalenaCloud does the fleet management and image distribution, etc. for us.
Our customer has a special request now. He wants us to use a special piece of hardware. It is a 32-bit Debian system. We already did manage to start balenaOS in a docker container (self-compiled 32bit Docker daemon with scripts from github.com/balena-os/balenaos-in-container). We cannot flash the whole hardware because of existing software that needs to run beside the balenaOS.
Now to the tricky part. Is it possible to mount/route the X-Server (/tmp/.X11-unix) from Debian to the balenaOS to the balenaService running to show content? We cannot start a new X-Server in the balenaService because the system has also some apps that need to be shown on the display.
We did modify the balena-in-container script already to forward the X-server into the balenaOS. The small step missing is the forwarding from balenaOS to the balenaService, which is running inside. We tried it with a docker-compose file to bind the X-Server(/tmp/.X11-unix) but only named-values are allowed in that file.
Are there any other options we could try to get the X-Server forwarded from balenaOS to that balenaService?