No dbus in /var/run, unable to run wifi-connect

Product support
1

When running Starter images, wifi-connect was working fine for me. I started to move into deployment with my first 20 systems and wifi-connect stopped working! The application is now Essentials. Nothing has indicated to me that dbus should stop working, but this is the error message I get from wifi-connect:

root@b18d456:/usr/src/app# ./wifi-connect 
Cannot get the NetworkManager service state
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: D-Bus error: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory (org.freedesktop.DBus.Error.FileNotFound)', /checkout/src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.

It looks like D-Bus setup failed: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory is the same issue.

However, looking at my docker-compose.yml, it seems it should be fine:

version: '2.1'
networks: {}
volumes:
  resin-data: {}
services:
  main:
    build:
      context: .
    privileged: true
    tty: true
    restart: always
    network_mode: host
    volumes:
      - 'resin-data:/data'
    labels:
      io.resin.features.kernel-modules: '1'
      io.resin.features.firmware: '1'
      io.resin.features.dbus: '1'
      io.resin.features.supervisor-api: '1'
      io.resin.features.resin-api: '1'

What’s going on here?

4

Doh.

My start.sh has the DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket setting. I’d missed this when trying to invoke from the command-line to debug. wifi-connect did start when I updated the path.