Guides

Update 200 kiosks without breaking them

Canaries first, then waves, stopping on failures. Offline kiosks catch up later.

Running an upgrade on every kiosk at once is how a bad package takes down a whole fleet. A fleet command runs it on a few first, then in waves, and stops on its own if too many fail.

1. Tag the kiosks

Give every kiosk a tag such as kiosk (and site:… if you want to go store by store). Tag them from each device's page, or with the API for many at once.

2. Choose what to run

In Commands → New command, pick Upgrade packages (apt, apk, dnf, zypper or pacman, without questions), Restart, or your own command, for example:

systemctl restart kiosk-app && systemctl is-active kiosk-app

The command's exit code decides success, so end with a check like is-active. Tick Save for next time to reuse it.

3. Set the waves

SettingFor 200 kiosksWhy
Canaries first2Run on two kiosks and wait for them before anyone else.
Devices at once20Ten waves; a bad change reaches 20 kiosks at most before it stops.
Stop if failures exceed (%)10Two failed kiosks in a wave of 20 stop the rest.
Timeout per device (seconds)600An upgrade that hangs counts as a failure.
Offline devicesRun if back within 24 hoursKiosks that are off tonight upgrade when they return.

4. Run it now or tonight

Pick Now, Once, later (say, 3 AM in your time zone, when stores are closed), Every day or Every week. Review shows how many devices it will reach before anything runs.

5. Read the results

The command page fills in per kiosk as each one finishes: ok, failed, timed out or waiting to come back online, with its output. Run again repeats it, for instance on the ones that failed once you've fixed the cause.

Commands run as the device's shell user. Package upgrades need root: install with --shell-user root, or give that account sudo without a password. See who the shell runs as.

Something wrong or missing on this page? Tell us.