balena-supervisor/.mochapodrc.yml
Christina Ying Wang 49ee1042a8 Mount boot partition into container on Supervisor start
As the Supervisor is a privileged container, it has access to host /dev, and therefore has access
to boot, data, and state balenaOS partitions. This commit sets up the framework for the following:

- Finds the /dev partition that corresponds to each partition based on partition label
- Mounts the partitions into set mountpoints in the device
- Removes reliance on env vars and mountpoints provided by host's start-balena-supervisor script
- Simplifies host path querying by centralizing these queries through methods in lib/host-utils.ts

This particular changes env vars for and mounts the boot partition.

Since the Supervisor would no longer rely on container `run` arguments provided by a host script,
this change moves Supervisor closer to being able to start itself (Supervisor-as-an-app).

Change-type: minor
Signed-off-by: Christina Ying Wang <christina@balena.io>
2023-03-27 12:07:01 -07:00

28 lines
986 B
YAML

# This defines default configuration that
# should apply to all mocha-pod/testfs instances
testfs:
# These are test files that need to be configured
# for all tests. The `from` defines where to find
# them in the local source. These can be overriden
# in the `testfs` configuration.
filesystem:
/mnt/boot:
os-release:
from: test/data/etc/os-release
config.json:
from: test/data/testconfig.json
config.txt:
from: test/data/mnt/boot/config.txt
device-type.json:
from: test/data/mnt/boot/device-type.json
# The `keep` list defines files that already exist in the
# filesystem and need to be backed up before setting up the test environment
keep: []
# The `cleanup` list defines files created by the tests that need to be removed
# when restoring the filesystem
cleanup:
- /data/database.sqlite
- /data/apps.json.preloaded
- /mnt/root/tmp/balena-supervisor/**/*.lock
- /mnt/boot/splash/*.png