Hey there, I’ve been trying to get my feet wet with BalenaOS.
I just got myself an Intel NUC, and I’ve been trying to follow the instructions at https://www.balena.io/os/docs/intel-nuc/getting-started/ using the current (2.50.1 rev1) Intel NUC dev image. While not everything happens preceisely as described, things seem to work up until the push.
When I try to “balena push balena.local”, I get
Could not communicate with local mode device at address 192.168.1.113 Additional information may be available with the `--debug` flag. For help, visit our support forums: https://forums.balena.io For bug reports or feature requests, see: https://github.com/balena-io/balena-cli/issues/
And with the --debug flag I get this:
Missing applicationOrDevice Error: Missing applicationOrDevice at C:\Program Files\balena-cli\client\node_modules\capitano\build\signature.js:150:29 at C:\Program Files\balena-cli\client\node_modules\capitano\node_modules\async\lib\async.js:181:20 at Immediate.iterate (C:\Program Files\balena-cli\client\node_modules\capitano\node_modules\async\lib\async.js:262:13) at runCallback (timers.js:705:18) at tryOnImmediate (timers.js:676:5) at processImmediate (timers.js:658:5) at process.topLevelDomainCallback (domain.js:126:23)
Looking at some older posts, I logged in using ssh and ran a few commands. Firstly, I noticed that when I asked for the “balena-engine version”, there seemed to be a problem with the engine daemon:
Client: Version: 18.09.17-dev API version: 1.39 Go version: go1.10.8 Git commit: 2ab17e0536b6a4528b33c75e8f350447e9882af0 Built: Mon May 11 15:17:45 2020 OS/Arch: linux/amd64 Experimental: false Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running?
Then, running some commands from an earlier post:
root@balena:~# balena-engine ps -a Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running? root@balena:~# journalctl -u resin-supervisor --no-pager -- Logs begin at Tue 2020-07-21 23:28:47 UTC, end at Tue 2020-07-21 23:56:45 UTC. -- Jul 21 23:35:21 localhost systemd: Dependency failed for Balena supervisor. Jul 21 23:35:21 localhost systemd: resin-supervisor.service: Job resin-supervisor.service/start failed with result 'dependency'. Jul 21 23:43:41 balena systemd: Dependency failed for Balena supervisor. Jul 21 23:43:41 balena systemd: resin-supervisor.service: Job resin-supervisor.service/start failed with result 'dependency'.
So, I’m hoping that someone can give me a hand, and help me to work out what’s up.
(A bit of honesty, I’ve also tried using Balena Cloud, but been unable to get past post provisioning; I’ve returned to this, as it seems more self-contained.)
Update: I have also noticed that when I restart the machine (after doing a “shutdown now” from the ssh logon), it still takes a very lonig time doing the “expand resin-data partition” step (perhaps half an hour or so). Is that to be expected? It feels like this is indicating something hasn’t been fully set up at this point.