I have successfully developed, released, updated, and managed my project on a test device using an openBalena architecture based on 2 VMs (a client with balena-cli and a server with openBalena).
However, in production environment, I don’t have internet access, so, I created another pair of VMs. I installed balena-cli, openBalena, and the necessary software (such as Docker), I removed internet access.
I re-flashed the device with the image containing references to the production environment using
sudo balena config inject config-prod.json --drive revpi-connect-4-6.1.24-v16.10.1.img
I see it online in the production environment. But I’m having trouble to deploy the application.
Initially, I tried simply building on the dev balena-cli machine balena build --fleet <slug>
, then docker save -o project.tar <docker_image>
, transferred it to the internet-isolated environment, then docker import project.tar
, and finally balena deploy <other-slug> <new_generated_docker_image_uuid>
but i get this error
[Error] Deploy failed
Get "https://registry2.DOMAIN.local/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Maybe it’s due to different certificates between openBalena dev and openBalena prod.
In both environments I use two different self-signed certificates.
I believe I need to refer to these guides:
- https://docs.balena.io/learn/more/masterclasses/advanced-cli/#13-separate-environment-configurations (Balena CLI Advanced Masterclass, 1.3 Separate Environment Configurations)
- https://docs.balena.io/learn/more/masterclasses/advanced-cli/#5-preloading-and-preregistering (Balena CLI Advanced Masterclass, 5. Preloading and Preregistering)
I’m lost and I don’t know if I’m going the right way.
Thanks in advance.
Andrea