I am currently using the Balena LivePush feature. Regardless of the host environment (Windows 10 Pro, Ubuntu 20.04 WSL2, or Native Ubuntu 20.04), I receive the following error message when a file change is detected that is preventing the automatic rebuild of the service.
[Error] There was an error rebuilding the service: TypeError: Cannot read property 'external' of undefined
I have three services for the fleet/application with a docker-compose.yml
file. This error occurs if I make a change in a file within the “backend” service. I have to do a CTRL+C from the terminal to kill the LivePush session and explicitly issue the balena push <SHORT-UUID>.local
command again, which usually requires rebuilding the entire service, not just the component/stage or that was modified.
Any information to resolve this issue or provide more details on the source of the issue would be greatly appreciated. Thank you.
Hello,
Can you please provide more details about your setup, particularly:
- which device type you are using?
- which balenaOS version it is running?
- which supervisor version the device is on?
- which balenaCLI version you are using on your development machine?
Thanks
@rahul-thakoor Thank you for responding, but back in January 2022, we changed our development workflow with our Balena-powered devices and no longer use the Balena LivePush feature. Thus, I have not used the feature since late December 2021 when I made the original post, and I am not sure if this issue is still relevant. Sorry, but I forgot I made this post.
However, in the interest of documenting and helping the community in case someone else encounters the error, here are answers to your questions:
- which device type you are using?
NVIDIA Jetson Nano DevKit (SD Card), NVIDIA Jetson Xavier NX DevKit (SD Card), and NVIDIA Jetson AGX Xavier DevKit (eMMC). The error was observed with all three Jetson devices running BalenaOS.
- which balenaOS version it is running?
Following the tags from Balena Jetson, this would be BalenaOS v2.88.4 and one of the “+revisions”. This is hard to know because we have upgraded all three devices. At the time, we were using the development variant for each one.
- which supervisor version the device is on?
We are pretty good at ensuring we are running the latest versions of the OS and Supervisor. According to Balena-Supervisor tags, the Supervisor version would have been v12.11.20, v12.11.21, or v12.11.22.
- which balenaCLI version you are using on your development machine?
At the time back in December, it would have been v12.55.X, I cannot be exact on the patch version, X
.