as i wrote last week here a “quick” reply - (sorry, got a little more text):
We changed the OS to BalenaOS, 64 Bit are working without any struggles, works almost without issues (see below). We are currently pushing local, but we will propably at least also investigate BalenaCloud to deploy our applications/microservices.
A short overview about what our project is currently doing, each now using Balena base images (We were able to shrink the used space by 70%):
- Jupyter (One is used as a “webservice” with jupyter_kernel_gateway and one as a notebook viewer service)
- MongoDB (Sadly currently not using a balena base image)
- Multiple OPC UA server
- UnityWebGL with OPC UA connections
- (Maybe also redirecting RaspPy sensor data inside a container, need to check if we can access sensor data inside docker at all)
I love that local livepush ability with balena-cli! We are now currently also able to develop on multiple OS (Win10, MacOS) without caring about the infrastructure behind, no setting up on every developer machine after installing docker.
Some issues currently (not critical, just to sum them up):
- We can’t use balena.local, i guess it’s an issue with dns, we have to use the ipv4 adress to push
- No host-volumes, we use them to develop on our docker containers (node_modules, Hot-Reloading) on our host. Current workaround: We comment out the volumes in our docker-compose.yml when we are deploying to a pi. Because of that we had to add the files, that would have been added by the mount, to the dockerfile build process.
- Everytime one of our mongo container stops (planned), it always restarts automatically on Pi. Stopped that behaviour with restart: on-failure in docker-compose.yml. Adding this here because the behaviour is different to the one if started in Docker Win10.