This guide explains how to update and run new versions of Fleet. For initial installation instructions, see Installing Fleet.
There are two steps to perform a typical Fleet update. If any other steps are required, they will be noted in the release notes.
As with any enterprise software update, it's a good idea to back up your MySQL data before updating Fleet.
Follow the binary update instructions corresponding to the original installation method used to install Fleet.
Download the latest raw Fleet binaries:
curl -O https://github.com/fleetdm/fleet/releases/latest/download/fleet.zip
Unzip the binaries for your platform:
# For a Darwin compatible binary
unzip fleet.zip 'darwin/*' -d fleet
./fleet/darwin/fleet --help
# For a Linux compatible binary
unzip fleet.zip 'linux/*' -d fleet
./fleet/linux/fleet --help
Replace the existing Fleet binary with the newly unzipped binary.
Pull the latest Fleet docker image:
docker pull fleetdm/fleet
Before running the updated server, perform necessary database migrations. It is always advised to back up the database before running migrations.
Database migrations in Fleet are intended to be run while the server is offline. Osquery is designed to be resilient to short downtime from the server, so no data will be lost from osqueryd clients in this process. Even on large Fleet installations, downtime during migrations is usually only seconds to minutes.
First, take the existing servers offline.
Run database migrations:
fleet prepare db
Note, if you would like to run this in a script, you can use the --no-prompt option to disable prompting before the migrations.
Start new Fleet server instances:
fleet serve