Installing on Linux from a terminal
Linux only ยท the download page's steps, as commands
Everything on the download page can be done without a terminal. This page is for people who prefer one, and for the times a desktop's own package installer gets in the way.
Install the package
Debian, Ubuntu and their relatives (.deb)
In the folder the file downloaded to:
sudo apt install ./borago-board_*.deb
The ./ matters: without it apt looks for a package of that name in its
repositories. If the system is still installing its own updates, which a new installation
does for a while after it first starts, apt waits for them to finish. That is why this
works where a desktop installer can say Done and install nothing (Kubuntu and Lubuntu
24.04).
Fedora and RHEL (.rpm)
sudo dnf install ./borago-board_*.rpm
openSUSE (.rpm)
sudo zypper install ./borago-board_*.rpm
Both packages add the Borago package repository, so later versions arrive with your
normal system updates (sudo apt upgrade, sudo dnf upgrade or
sudo zypper update).
AppImage
chmod +x BoragoBoard-*.AppImage
./BoragoBoard-*.AppImage
Only for the first launch: the app's own updates keep the file runnable.
The AppImage mounts itself with FUSE, which desktop Linux installs already have. You do
not need libfuse2, because the AppImage carries its own copy. If it exits
with fuse: device not found, install FUSE:
sudo apt install fuse3
On Fedora and RHEL that package is fuse3 too
(sudo dnf install fuse3). The .deb and .rpm packages do not need FUSE at
all.
About AppImage and FUSE
Docker
On Ubuntu, Debian and Fedora based systems Borago Board installs Docker for you, with the gVisor sandbox, behind one password prompt and with no log-out afterwards. To do it yourself instead:
Ubuntu and Debian based
sudo apt-get update
sudo apt-get install -y docker.io docker-compose-v2 docker-buildx
sudo systemctl enable --now docker
sudo usermod -aG docker $USER
Fedora
sudo dnf install -y moby-engine docker-compose docker-buildx
sudo systemctl enable --now docker
sudo usermod -aG docker $USER
Then log out and back in. A group change only reaches new logins, so until then Docker
still refuses your user. Anywhere else, follow Docker's
Install guide
and then run the usermod line above. For the gVisor sandbox by hand, see
gVisor's install guide.
Removing it
Removing the app leaves your boards, project files and containers in place, on purpose. What stays behind, and how to remove it