balena-supervisor/docker-compose.yml

version: '2.1'

services:
  # This service can only be named `main` or `balena-supervisor` as older
  # devices will keep relying on the `/v6/supervisor_release` endpoint that
  # identifies the supervisor image by that service name.
  balena-supervisor:
    build: ./
    privileged: true
    tty: true
    restart: always
    network_mode: host
    labels:
      io.balena.features.balena-api: '1'
      io.balena.features.dbus: '1'
      io.balena.features.balena-socket: '1'
      io.balena.features.kernel-modules: '1'
Add supervisor docker-compose This will allow the supervisor service to be correctly named on the API Change-type: patch 2021-09-29 15:50:48 +00:00			`version: '2.1'`

			`services:`
			# This service can only be named `main` or `balena-supervisor` as older
			# devices will keep relying on the `/v6/supervisor_release` endpoint that
			`# identifies the supervisor image by that service name.`
			`balena-supervisor:`
			`build: ./`
			`privileged: true`
			`tty: true`
			`restart: always`
			`network_mode: host`
			`labels:`
			`io.balena.features.balena-api: '1'`
			`io.balena.features.dbus: '1'`
			`io.balena.features.balena-socket: '1'`
Use compose long syntax for /lib/firmware and /lib/modules As /lib/firmware and /lib/modules are always expected to be in the host filesystem, using long syntax ensures that the Supervisor container cannot start on an invalid host. (Long syntax volumes error when the host path does not exist, whereas short syntax volumes create the host path.) Change-type: major Closes: #1965 Signed-off-by: Christina Wang <christina@balena.io> 2022-06-14 17:54:11 +00:00			`io.balena.features.kernel-modules: '1'`