CameronDiver
CameronDiver
We will have variables like `BALENA_HOST_UDEV_11='some udev rule` and these should be applied by the supervisor. This supercedes https://github.com/balena-io/balena-supervisor/issues/880.
Currently, doing a `os-config leave` will stop the running application. Instead we want that application to keep running, as long as the images are available on device.
Assuming that the "package" passed to the supervisor api will container Docker images, and a target state, use the existing local mode infrastructure to apply this update without needing a...
According to https://forums.balena.io/t/developing-on-a-balena-device/8134 running a `balena stop` on-device, and then pushing changes in services to a balena device running local mode, not all of the services are started back up....
This comes from the following: https://github.com/sidorares/dbus-native/issues/271#issuecomment-580262777 The fix it seems would be to move away from dbus-native. A possible replacement is https://github.com/Shouqun/node-dbus which does not rely on `put`.
Depends on: https://github.com/balena-io/balena-supervisor/issues/1064 We should allow users to specify the maximum amount of times that the supervisor should attempt to download an image or a delta, and the interval between...
This would control whether the device will start downloading an image, whereas update lock controls whether a device should install an update.
The fix for this is to push a release which is not blocked with a container contract.
This means that changes in the host should be mirrored into the container, but they should never be mirrored back. This should be switched on by a label on the...
The supervisor should mount both removable storage which is present at boot, and any hot-plugged storage and mount it into `/media` on the OS. Any services which specify the `io.balena.features.external-storage`...