balena devices supported returns a empty list and cannot build any app anymore

openBalena
1

I just updated the OpenBalena to version v3.4.1 (latest version available right now) and using the latest balena-cli, version 12.46.2 but after I’m successfully logging in and try to run the following command: balena devices supported I get no device list.

Is there any additional setup that I’m not aware of?

Previous issue affects the way that I’m building the apps, using:

DEBUG=1 balena build --deviceType raspberry-pi --arch rpi --emulated
[debug] original argv0="balena" argv=[/home/user/balena-cli/balena,/snapshot/versioned-source/bin/balena,build,--deviceType,raspberry-pi,--arch,rpi,--emulated] length=8
[debug] new argv=[/home/user/balena-cli/balena,/snapshot/versioned-source/bin/balena,build,--deviceType,raspberry-pi,--arch,rpi,--emulated] length=8
[Debug]   Parsing input...
[Debug]   Loading project...
[Debug]   Resolving project...
[Debug]   docker-compose.yml file found at "/home/user/myProject"
[Debug]   Creating project...
[Info]    Building for rpi/raspberry-pi
[Build]   Building services...
[Build]   wifi-connect Preparing...
[Build]   node-red     Preparing...
[Build]   google-iot   Preparing...
[Info]    Emulation is enabled
Killed

docker-compose.yml looks like:

version: '2.1'

services:
  wifi-connect:
    build: ./wifi-connect
    restart: always
    network_mode: host
    privileged: true
    labels:
      io.balena.features.dbus: '1'
      io.balena.features.firmware: '1'
    environment:
      PORTAL_SSID: 'AValue'
      PORTAL_PASSPHRASE: 'APasswordValue'
      BALENA_ARCH: rpi
      BALENA_MACHINE_NAME: raspberry-pi

  node-red:
    build: ./node-red/node-red
    volumes:
      - 'volume-data:/data'
    restart: always
    privileged: true
    network_mode: host
    labels:
      io.balena.features.supervisor-api: '1'
    cap_add:
      - SYS_RAWIO
    devices:
      - "/dev/mem:/dev/mem"
      - "/dev/gpiomem:/dev/gpiomem"
      - "/dev/i2c-1:/dev/i2c-1"
      - "/dev/ttyUSB0:/dev/ttyUSB0"
    expose:
      - "80"
    depends_on:
      - "google-iot"
    command: ["./wait-for-it/wait-for-it.sh", "google-iot:8883", "--", "echo", "Google IoT Service is up and running"]
    environment:
      USERNAME: 'AValume'
      PASSWORD: 'AHashedPAsswordValue'
      PORT: 1234

  google-iot:
    build: ./google-iot
    volumes:
      - 'volume-data:/data/google-iot'
    restart: always
    privileged: true
    network_mode: host
    depends_on:
      - "wifi-connect"
    command: ["./wait-for-it/wait-for-it.sh", "www.google.com:80", "--", "echo", "IoT device is connected to the internet!"]
    expose:
      - 8883
    environment:
      BALENA_MACHINE_NAME: raspberry-pi
      GOOGLE_IOT_PROJECT: myproject
      GOOGLE_IOT_REGION: my-region
      GOOGLE_IOT_REGISTRY: my-registry
      GOOGLE_IOT_SERVICE_ACCOUNT_TOKEN: 'json-account-token'

volumes:
  volume-data:

I get

balena-cli logs:

user@ubuntu:~/myProject$ balena devices supported
SLUG ALIASES ARCH NAME
user@ubuntu:~/myProject$ balena --version
12.46.2

OpenBalena logs:

balena@cloud:~/open-balena$ docker ps -a
CONTAINER ID   IMAGE                                 COMMAND                  CREATED          STATUS          PORT
S                                                                                                             NAMES
879a051c9071   openbalena_haproxy                    "/docker-entrypoint.…"   44 minutes ago   Up 18 minutes   0.0.
0.0:80->80/tcp, :::80->80/tcp, 222/tcp, 3128/tcp, 5432/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 6379/tcp   openb
alena_haproxy_1
37e628f69c00   balena/open-balena-vpn:v9.17.11       "/usr/bin/entry.sh"      44 minutes ago   Up 18 minutes   80/t
cp, 443/tcp, 3128/tcp                                                                                         openb
alena_vpn_1
5537263ac70b   balena/open-balena-api:v0.139.0       "/usr/bin/entry.sh"      44 minutes ago   Up 18 minutes   80/t
cp                                                                                                            openb
alena_api_1
f2448226a57b   balena/open-balena-registry:v2.16.1   "/usr/bin/entry.sh"      44 minutes ago   Up 18 minutes   80/t
cp                                                                                                            openb
alena_registry_1
cb1356e7d194   openbalena_cert-provider              "/entry.sh /usr/src/…"   44 minutes ago   Up 18 minutes   80/t
cp                                                                                                            openb
alena_cert-provider_1
26855836641b   balena/open-balena-s3:v2.9.9          "/usr/bin/entry.sh"      44 minutes ago   Up 18 minutes   80/t
cp                                                                                                            openb
alena_s3_1
269449e0449c   redis:alpine                          "docker-entrypoint.s…"   44 minutes ago   Up 18 minutes   6379
/tcp                                                                                                          openb
alena_redis_1
ffb2fd2251e1   balena/open-balena-db:v4.1.0          "/balena-entrypoint.…"   44 minutes ago   Up 18 minutes   5432
/tcp                                                                                                          openb
alena_db_1
2

Solved by increasing the memory, I was using a VM (Ubuntu) and increased the VM memory to 8GB.

4

Hi, I get the same issue. I tried with docker and kubernetes. Both fail (system with 8GB RAM). Is there anything else you tried here @elsevero