Skip to content

Update

sudo ./install.sh update updates a manager or a remote sensor in place to the version of the checked-out installer. Persona, baits, admin token, enrolled sensors and the database are kept.

From To How
1.0.0 1.0.1 sudo ./install.sh update
v0.3.x / v0.4.x 1.0.x not supported in place: sudo ./install.sh uninstall with the old version, then a fresh install

Steps

Update the manager first, then each remote sensor:

cd ReD-Pot
git pull                      # or: git checkout v1.0.1
sudo ./install.sh update      # --yes for unattended runs

What the update does

  1. Reads the installed version and refuses anything but a supported step. On the current version it says "already up to date" and changes nothing. The previous image must still be on the host.
  2. Backs up first, to /var/backups/redpot/<time>-<manager|sensor>-<version>/ (root only): the database (copied with the SQLite backup API while the console runs, then checked), rpot.json or conf/sensor.json, installer.json, docker-compose.yml, firewall.sh and the systemd unit, with each file's owner and mode. Ctrl+C up to here changes nothing.
  3. Gets the new image (verified download, or a local build).
  4. Manager: writes the new compose file, firewall.sh and unit, applies the rules without a gap, restarts, and checks that the console answers and every decoy passes the self-test. Sensor: changes the image tag and restarts; the relay and decoy must be running. Signals (Ctrl+C, a dropped SSH session) are ignored during this part.
  5. On any failure the previous files are restored with their owners and modes, and the service restarts with the previous image and firewall rules. "ROLLED BACK" is printed only once the service runs again; otherwise the output says what is wrong and where the backup is.

Interrupted update

If an update is cut off (power loss, kill -9), the next sudo ./install.sh update offers to roll it back first (default no; unattended: --yes --resume-rollback). It refuses if the files were changed after the cut-off update. Until then, add-decoy, remove-decoy and set-access refuse to run.

Clean up

sudo ./install.sh uninstall removes the update backups of that install (--keep-data keeps them). Delete an old backup directory under /var/backups/redpot/ and the previous image (sudo docker image rm rpot:1.0.0) when you no longer need them.

Enterprise feature: available in ReD-Pot Enterprise

Signed offline install and update bundles. Enterprise installs and updates from one signed file that holds the installer, the image and a signed manifest. Nothing is downloaded during the install, and the signature is checked before any code from the new bundle runs. The licence is a signed offline file as well.

About ReD-Pot Enterprise · Compare editions · Contact us for a licence