The problem with Getting-Started

Hello,

I’m trying to go through “getting started” guide (https://www.balena.io/os/docs/raspberrypi3/getting-started/) and got this message on the deploy stage:

The supervisor version on this remote device does not support multicontainer local mode. Please update your device to balenaOS v2.20.0 or greater from the dashboard.

Additional information may be available by setting a DEBUG=1 environment
variable: “set DEBUG=1” on a Windows command prompt, or “export DEBUG=1”
on Linux or macOS.

If you need help, don’t hesitate in contacting our support forums at
https://forums.balena.io

For bug reports or feature requests, have a look at the GitHub issues or
create a new one at: https://github.com/balena-io/balena-cli/issues/

But the OS version is BalenaOS 2.43.0+rev1 Dev (i have double-checked this)

Alex

Hey @letrich would be good if you could help with a bit more info to try to triage the issue.

  • Is your device on balenaCloud, or is it standalone?
  • what version of the balena CLI are you using? (can check with balena version)
  • what command/state is when you run into the issue exactly?

My hunch is that on that page the getting started might be a bit out of date (regarding local push, at least) and there can be some information we haven’t updated yet / missed to incldue.

Hi @imrehg

My device is not in the belanaCloud, I want to test standalone.
I have downloaded balena dev image from balena os page
Balena CLI version is 11.17.0 (standalone linux binnary from github)
I can successfully ssh to my device with “balena ssh mydevice.local
Next, I git clone this repo: https://github.com/balena-io-projects/multicontainer-getting-started.git
After that, in cloned repo:
balena push mydevice.local

[debug] original argv0=“balena” argv=[/home/letrich/balena-cli/balena,/snapshot/versioned-source/bin/balena,push,mydevice.local] length=4
[debug] Using . as build source
[Debug] Checking we can access device
[Debug] Sending request to http://mydevice.local:48484/ping
The supervisor version on this remote device does not support multicontainer local mode. Please update your device to balenaOS v2.20.0 or greater from the dashboard.

If you need help, don’t hesitate in contacting our support forums at
https://forums.balena.io

For bug reports or feature requests, have a look at the GitHub issues or
create a new one at: https://github.com/balena-io/balena-cli/issues/

Hi @letrich that is very strange. When you are ssh’d into the device can you run balena-engine ps -a and see what version of the supervisor is running. Also if you could pull the logs from the supervisor using journalctl -u resin-supervisor --no-pager that would be helpful as well.

Hi @shaunmulligan,
balena-engine ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d0946313fcce hello-world “/hello” 5 seconds ago Up Less than a second romantic_austin
354c4bd5ea67 balena/armv7hf-supervisor:v10.2.2 “./entry.sh” 3 days ago Up 9 minutes (healthy) resin_supervisor

journalctl -u resin-supervisor --no-pager

– Logs begin at Thu 2019-08-08 09:59:55 UTC, end at Mon 2019-10-28 03:29:09 UTC. –
Oct 28 03:18:47 mydevice systemd[1]: Starting Resin supervisor…
Oct 28 03:18:47 mydevice resin-supervisor[1226]: resin_supervisor
Oct 28 03:18:47 mydevice resin-supervisor[1234]: active
Oct 28 03:18:47 mydevice systemd[1]: Started Resin supervisor.
Oct 28 03:18:54 mydevice resin-supervisor[1235]: Container config has not changed
Oct 28 03:18:58 mydevice resin-supervisor[1235]: Starting system message bus: dbus.
Oct 28 03:18:58 mydevice resin-supervisor[1235]: * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
Oct 28 03:18:58 mydevice resin-supervisor[1235]: …done.
Oct 28 03:19:09 mydevice resin-supervisor[1235]: [info] Supervisor v10.2.2 starting up…
Oct 28 03:19:09 mydevice resin-supervisor[1235]: (node:1) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Oct 28 03:19:09 mydevice resin-supervisor[1235]: [debug] Starting event tracker
Oct 28 03:19:09 mydevice resin-supervisor[1235]: [debug] Starting api binder
Oct 28 03:19:09 mydevice resin-supervisor[1235]: [debug] Unmanaged mode is set, skipping API client initialization
Oct 28 03:19:09 mydevice resin-supervisor[1235]: [debug] Starting logging infrastructure
Oct 28 03:19:09 mydevice resin-supervisor[1235]: [event] Event: Supervisor start {}
Oct 28 03:19:09 mydevice resin-supervisor[1235]: [debug] Performing database cleanup for container log timestamps
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [info] Starting up in unmanaged mode, activating local mode
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [info] Switching logging backend to LocalLogBackend
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [debug] Storing engine snapshot in the database. Timestamp: 2019-10-28T03:19:10.098Z
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [debug] Connectivity check enabled: true
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [debug] No API endpoint specified, skipping connectivity check
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [debug] Starting periodic check for IP addresses
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [info] Reporting initial state, supervisor version and API info
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [debug] Handling of local mode switch is completed
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [info] Attempting to load preloaded apps…
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [info] Starting API server
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [info] Applying target state
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [info] Unmanaged mode is set, skipping API binder initialization
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [debug] Supervisor API listening on all interfaces
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [debug] Finished applying target state
Oct 28 03:19:10 mydevice resin-supervisor[1235]: [success] Device state apply success
Oct 28 03:23:59 mydevice resin-supervisor[1235]: [api] GET /v1/healthy 200 - 42.060 ms
Oct 28 03:29:01 mydevice resin-supervisor[1235]: [api] GET /v1/healthy 200 - 18.739 ms
Oct 28 03:29:09 mydevice resin-supervisor[1235]: [debug] Attempting container log timestamp flush…
Oct 28 03:29:09 mydevice resin-supervisor[1235]: [debug] Container log timestamp flush complete

One additional string appeard after i tried to push app again:

Oct 28 03:30:53 mydevice resin-supervisor[1235]: [api] GET /ping 200 - 19.629 ms

Hi, can you check that you don’t have more than one device named mydevice.local on the local network? You can check this by running sudo balena scan command.

Could not find any balenaOS devices in the local network

Additional information may be available by setting a DEBUG=1 environment
variable: “set DEBUG=1” on a Windows command prompt, or “export DEBUG=1”
on Linux or macOS.

If you need help, don’t hesitate in contacting our support forums at
https://forums.balena.io

For bug reports or feature requests, have a look at the GitHub issues or
create a new one at: https://github.com/balena-io/balena-cli/issues/

It is very strange, I still can ssh to mydevice.local.
I’m using balena-cli inside windows wsl2. Could it be the reason?

UPD: I have installed balena-cli on windows 10. The same behaviour - can SSH, but no devices with “balena scan”

Alex

hi there! A balena scan requires privileged access to network interfaces. Can you confirm you re issuing that command in privileged mode?

hi,
Yes, I use it with sudo in wsl and admin mode for powershell.
For non-priveleged mode i getting another message about priveleges.
Can anyone from balena team just repeat instructions in getting-started guide to ensuresure that problem at my side?

Hello,
We didn’t manage to reproduce your issue on our side.
Might there be another balena device named mydevice.local on the same network?
Could you please try balena push <DEVICE_IP_ADDRESS> ?

Hi @zvin,
“balena push <DEVICE_IP_ADDRESS>” works for me! Thank you!
Alex