Maintenance & updates

Updating an instance, and getting it running again when it stumbles.

Updating #

The procedure depends on how you installed. In every case, your configuration, your data and your secrets are preserved.

# run the very same command as at install time
curl -fsSL https://raw.githubusercontent.com/kubuno/docker/main/install.sh | sudo bash

sudo apt install ./kubuno-core_*_amd64.deb
sudo systemctl restart kubuno

sudo dnf upgrade ./kubuno-core-*.x86_64.rpm
sudo systemctl restart kubuno

# run the installer for the new version
kubuno-core-setup-<version>-x64.exe

sudo installer -pkg kubuno-core-<version>-arm64.pkg -target /

Note

The Docker installation updates on its own every night, unless you installed it with --no-auto-update.

In which order #

The core first, the modules afterwards: a module requires a core whose version is at least its own. Modules are updated one by one, from the console or through their packages.

Before an update #

Back up the database and the files — the Backup page gives the command. Schema migrations are applied automatically at startup, and they are never replayed backwards.

If the service refuses to restart #

systemctl status kubuno
journalctl -u kubuno -n 50

# after several reinstallations in a row, systemd may block restarts
sudo systemctl reset-failed kubuno
sudo systemctl restart kubuno