mirror of
https://github.com/balena-os/balena-supervisor.git
synced 2024-12-25 00:11:06 +00:00
97 lines
5.3 KiB
Markdown
97 lines
5.3 KiB
Markdown
---
|
|
title: Application update locks
|
|
excerpt: Locking application updates on your balenaOS devices
|
|
---
|
|
|
|
# Application update locks
|
|
|
|
Locking updates means that the balena supervisor will not be able to kill your application. This is meant to be used at critical sections of your code where you don't want to be interrupted, or to ensure that updates are only installed at certain times.
|
|
|
|
In order to do this, users can create a lockfile in a way that it has exclusive access, which will prevent the device supervisor from killing and restarting the app. As with any other lockfile, the supervisor itself will create such a file before killing the app, so you should only create it in exclusive mode. This means that the lockfile should only be created if it doesn't already exist. The exclusive access is achieved by opening the lockfile with the [O_EXCL and O_CREAT flags](https://linux.die.net/man/3/open), and several tools exist to simplify this process with examples given [below](#creating-the-lockfile).
|
|
|
|
For multicontainer applications, a release will only be updated if all of the services can be updated. While locks are per-service, having the update lock in a single service will prevent all services from updating to a new release.
|
|
|
|
The presence of a lockfile will ensure that your application does not get killed, but updates will still be downloaded by the supervisor, ready to be applied once the lockfile no longer exists.
|
|
|
|
### Location of the lockfile
|
|
|
|
On devices running supervisor 7.22.0 and higher, the lockfile is located at `/tmp/balena/updates.lock`. This lock is cleared automatically when the device reboots, so the user app must take it every time it starts up.
|
|
|
|
On older devices (with v4.0.0 <= supervisor version < v7.22.0) the lock is located at `/tmp/resin/resin-updates.lock`. The latest supervisor versions still take the lock at this legacy path for backwards compatibility.
|
|
|
|
Legacy supervisors (< v4.0.0) have the lock at `/data/resin-updates.lock`. This lock is only supported on devices running balenaOS 1.X.
|
|
This old lock has the problem that the supervisor has to clear whenever it starts up to avoid deadlocks. If the user app
|
|
has taken the lock before the supervisor starts up, the lock will be cleared and the app can operate under the false
|
|
assumption that updates are locked (see [issue #20](https://github.com/balena-os/balena-supervisor/issues/20)). We therefore strongly recommend switching to the new lock location as soon as possible.
|
|
|
|
### Creating the lockfile
|
|
|
|
There are many different tools and libraries to provide proper lockfile functionality and a few common examples are shown below.
|
|
|
|
__Note:__ Just creating the lockfile, for example by using `touch /tmp/balena/updates.lock`, is not adequate to prevent updates. A file created in this way won't have the exclusive access flag set, and thus does not provide reliable locking.
|
|
|
|
#### Shell
|
|
|
|
One simple way to create a lockfile is using [lockfile](https://linux.die.net/man/1/lockfile) (available for example in Debian from the `procmail` package):
|
|
|
|
```shell
|
|
lockfile /tmp/balena/updates.lock
|
|
# ... (do things)
|
|
rm -f /tmp/balena/updates.lock
|
|
```
|
|
|
|
Another tool is [flock](https://linux.die.net/man/1/flock) (available for example in Debian from the `linux-utils` package):
|
|
|
|
```shell
|
|
flock /tmp/balena/updates.lock -c '... (command to run while locked)'
|
|
```
|
|
|
|
For more examples and explanation of the functionality, check the links to the specific tools above.
|
|
|
|
#### Javascript
|
|
|
|
Using the [`lockfile` library](https://www.npmjs.com/package/lockfile), the lock can be acquired like in this example:
|
|
```javascript
|
|
import lockFile from 'lockfile';
|
|
|
|
lockFile.lock('/tmp/balena/updates.lock', function(err) {
|
|
// A non-null err probably means the supervisor is about to kill us
|
|
if (err != null) { throw new Error('Could not acquire lock: ', err); }
|
|
|
|
// Here we have the lock, so we can do critical stuff:
|
|
doTheHarlemShake();
|
|
|
|
// Now we release the lock, and we can be killed again
|
|
return lockFile.unlock('/tmp/balena/updates.lock', function(err) {
|
|
// If err is not null here, something went really wrong
|
|
if (err != null) { throw err; }
|
|
});
|
|
});
|
|
```
|
|
|
|
#### Python
|
|
|
|
In Python you can use the [`lockfile` library][lockfile-library]
|
|
```python
|
|
from lockfile import LockFile
|
|
lock = LockFile("/tmp/balena/updates")
|
|
with lock:
|
|
print lock.path, 'is locked.'
|
|
```
|
|
Check the link for more examples and other Python libraries that provide locking.
|
|
|
|
### Overriding the lock
|
|
|
|
The update lock can be overridden in case you need to force an update, for instance, if your app has hung in a critical section.
|
|
|
|
To do this the device or fleet must have `BALENA_SUPERVISOR_OVERRIDE_LOCK` configuration variable set to "1".
|
|
|
|
The easiest way to do this is to use the 'Override the update lock ...' toggle in the [Fleet or Device Configuration][device-configuration] page. Go to the configuration page of the device or fleet, locate the 'Override the update lock ...' item, click the activate button, and set the toggle to enabled. Disable the toggle afterwards in order to restore the update locks.
|
|
|
|
Also, you can programatically do this by hitting the `/v1/update` endpoint of the [supervisor HTTP API][supervisor-api], with `{ "force": true }` as body.
|
|
|
|
|
|
[device-configuration]:/learn/manage/configuration/#managing-device-configuration-variables
|
|
[supervisor-api]:/reference/supervisor/supervisor-api
|
|
[lockfile-library]:http://pythonhosted.org/lockfile/lockfile.html#examples
|