The wifi-connect block is a docker image that runs wifi-connect which is a utility for dynamically setting the WiFi configuration on a Linux device via a captive portal.

To use this image, create a service in your docker-compose.yml file as shown below:

version: "2.1"

services:
  wifi-connect:
    image: balenablocks/wifi-connect:<device arch name>
    restart: always
    network_mode: host
    privileged: true
    labels:
      io.balena.features.dbus: "1"
      io.balena.features.firmware: "1"

You can also set your docker-compose.yml to build a Dockerfile.template file, and use the build variable %%BALENA_ARCH%% so that the correct image is automatically built for your device arch (see supported architectures):

docker-compose.yml:

version: "2.1"

services:
  wifi-connect:
    build: ./
    restart: always
    network_mode: host
    privileged: true
    labels:
      io.balena.features.dbus: "1"
      io.balena.features.firmware: "1"

Dockerfile.template

FROM balenablocks/wifi-connect:%%BALENA_ARCH%%

balenablocks/wifi-connect is built for the following archs:

• aarch64
• armv7hf
• amd64
• rpi

balenablocks/wifi-connect can be configured via the following variables:

You can refer to the docs on how to set environment or service variables

Alternatively, you can set them in the docker-compose.yml or Dockerfile.template files.

When the container run, it executes the start.sh script. If the default logic does not suit your use case, you can adapt the script and replace the file in the image. You will have to set up the Dockerfile.template file as illustrated above and use the COPY directive and replace the file at /start.sh.

Note: This is a minimal image containing only the required dependencies and busybox. You will have to make use of the minimal toolset that busybox provides. Available commands.