Again bear with me as I’m postulating things.
Two questions as I look into Balena as a solution for our next gen. of Managed Devices.
My understanding is that the best practice for Balena (and Docker in General) is to minimize activity on the Host OS as much as possible. Under this premise.
a) I need additional VPN connections to be deployed.
Will deploying an OVPN container on top of the BalenaOS and it’s own VPN connection cause grief?Am I best to simply work on the Host OS (obviously prefer not to).
b) I’m coming from an “appliance” type platform history. On these appliances we have a filesystem path that contains the meat of the devices management tools etc etc. I would like to be able to treat this filesystem path i.e. “/opt/ourtoolset” as a image/container onto itself so that it can be tagged/patched/upgraded and downgraded easily. In essence a pre-populated volume that simply get’s pulled like all the other layers when deploying containers onto the host. In reading up on Docker it appears that an External Volume might do the trick. If I’ve managed to make my needs at all clear any guidance would be appreciated. Also I would need some on device persistence as well so I this “containerized” volume would also need to be able to interact with other containers.