Software

Maintenance → Software shows the selected node's platform software and MangoBoost packages. To compare and upgrade all nodes, use Updates; for DPU firmware, see DPU Firmware Update.

Platform Inventory

The platform card shows OS, kernel, GPU driver, Docker and containerd versions. Show versions lists SDK packages that differ from the most common version.

SDK Packages and Sources

On the MangoBoost SDK card, operator and admin can install, upgrade and remove packages. Upgrades install the newest version in the node's source, set in Edit sources.

Distribution and other-vendor packages are listed separately without SDK actions. Upgrade all is blocked when any such package is installed. Older agents may not report origin; removing a version that looks like a distribution/vendor build then requires typing its package name. Only one package job runs on a node at a time.

Upgrade all can downgrade a newer build; check source versions first. If a job's status is unknown, check the node before retrying.

Repository Files and Signing

If a job fails with No SDK source version available, set the source in Edit sources. It manages /etc/apt/sources.list.d/mango.list or mango.sources on Ubuntu, not the installation guide's mango-sdk.sources.

New APT sources default to signature verification with /etc/apt/trusted.gpg.d/mango-sdk.gpg; install that keyring before the first package install (step 2 of the installation guide). Existing sources retain their signing keys, options and disabled entries when saved. On RHEL-family hosts the editor uses yum repository format, with gpgcheck=1 by default. Skip signature verification (not recommended) is an explicit per-source choice; keep verification enabled for signed repositories. MAC_SDK_REPO_KEY_URL on the master supplies the key URL shown in the editor and the default yum gpgkey.

Export

Export CSV saves the reported software.