Install BLOON on Linux
The Linux version of the application is currently in beta. We have tested the core features of BLOON as thoroughly as possible. If you encounter any issues during use, please feel free to contact us at support@bloon.io.
The BLOON Linux application currently only provides a desktop (GUI) version. A pure command-line (CLI, headless) version is under active development. Stay tuned!
Install using Debian Package Manager (.deb)
If your system uses the Debian package management system (e.g., Ubuntu, Debian, Linux Mint, etc.), you can use this method to install.
Install using RPM Package Manager (.rpm)
If your system uses the RPM package management system (e.g., Fedora, Rocky Linux, openSUSE, etc.), you can use this method to install.
Install using Script
Regardless of the package management system your system uses, you can use this method to install.
Increase File Watch Limit
If you experience issues with file modifications not syncing correctly when managing a large number of files with BLOON, it may be due to the system's file watch limit. You can refer to this section to resolve the issue.
Click the button below to download the DEB installation package:
After downloading, you can verify the security and integrity of the installation package.
Use the following command to install:
sudo dpkg -i ./bloon_[version]_amd64.deb
Replace [version] with the version number of the DEB installation package you downloaded.
If your system lacks the required dependencies, you may see an error message similar to the following:
dpkg: dependency problems prevent configuration of bloon:
bloon depends on policykit-1; however:
Package policykit-1 is not installed.
dpkg: error processing package bloon (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
bloon
Don't worry, you can run the following command to automatically install the missing dependencies:
sudo apt-get install -f
Click the button below to download the RPM installation package:
After downloading, you can verify the security and integrity of the installation package.
If your system uses DNF (Dandified YUM) to manage packages (e.g., Fedora, Rocky Linux, etc.), you can use the following command to install:
sudo dnf install ./bloon-[version].x86_64.rpm
Replace [version] with the version number of the RPM installation package you downloaded.
If your system is openSUSE, you can use the following command to install:
sudo zypper install ./bloon-[version].x86_64.rpm
Replace [version] with the version number of the RPM installation package you downloaded.
Regardless of the package management system your system uses, you can use the following command to install:
wget --https-only --secure-protocol=TLSv1_2 -qO- https://raw.githubusercontent.com/bloon-io/bloon-install/refs/heads/main/bloon-install.sh | sh
The above is a single command; please execute it as one line.
The above command will use the bloon-install.sh script to automatically download the BLOON installation package in TGZ (tar & gzip) format, extract it, and install it to the appropriate location.
The bloon-install.sh script implements the method described in the Verify the Security and Integrity of the Installation Package section for verification. Please refer to that section for details. Alternatively, you may want to check the contents of the bloon-install.sh script yourself.
You can download BLOON's GPG key and the PGP signature file for the current installation package from the following links:
BLOON's GPG Key:
https://www.bloon.io/security/bloon-release-key.gpg
PGP Signature File for the Latest DEB Installation Package:
https://dl.bloon.io/dl-hero?pkg=deb&asc
Friendly reminder: The corresponding DEB installation package is here https://dl.bloon.io/dl-hero?pkg=deb. You may have already downloaded it in the Install using DEB section.
PGP Signature File for the Latest RPM Installation Package:
https://dl.bloon.io/dl-hero?pkg=rpm&asc
Friendly reminder: The corresponding RPM installation package is here https://dl.bloon.io/dl-hero?pkg=rpm. You may have already downloaded it in the Install using RPM section.
Then, you can use the following command to verify the PGP signature of the installation package:
gpg --no-default-keyring --keyring ./bloon-release-key.gpg --verify ./[installation_package_file].asc ./[installation_package_file]
The following example demonstrates the complete verification process of a DEB installation package:
# This command will download the file bloon-release-key.gpg
wget https://www.bloon.io/security/bloon-release-key.gpg
# This command will download the file bloon_1.4.0_amd64.deb
wget --content-disposition https://dl.bloon.io/dl-hero?pkg=deb
# This command will download the file bloon_1.4.0_amd64.deb.asc
wget --content-disposition "https://dl.bloon.io/dl-hero?pkg=deb&asc"
gpg --no-default-keyring --keyring ./bloon-release-key.gpg --verify ./bloon_1.4.0_amd64.deb.asc ./bloon_1.4.0_amd64.deb
Note: 1.4.0 is a demonstration version number; please replace it with the version number of the latest installation package you downloaded.
After execution, you will see a message similar to the following:
gpg: Signature made Thu 13 Feb 2025 05:15:22 AM PST
gpg: using RSA key C89F956472FBBE40A5BF4AA2F4DF8C43B4BB8D49
gpg: /home/myaccount/.gnupg/trustdb.gpg: trustdb created
gpg: Good signature from "LEXIPON CO., LTD. (Release key) <support@lexipon.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: C89F 9564 72FB BE40 A5BF 4AA2 F4DF 8C43 B4BB 8D49
The Good signature indicates that the signature of the file bloon_1.4.0_amd64.deb is valid. This means the file was indeed signed by the public key C89F956472FBBE40A5BF4AA2F4DF8C43B4BB8D49, and the file has not been tampered with since signing. This confirms the integrity of the file.
The warning WARNING: This key is not certified with a trusted signature! appears because the public key used to sign the file (bloon-release-key.gpg) is not certified by any trusted key on your system. Therefore, GPG cannot confirm whether this public key truly belongs to LEXIPON CO., LTD. (Release key) <support@lexipon.com>. This warning does not necessarily indicate a security risk; it simply means that your system does not have a trusted certification for the key.
The BLOON service is operated and maintained by LEXIPON CO., LTD. Please see our Privacy Policy for more information.
Regarding this, you can use the following command to print the fingerprint of BLOON's GPG key:
wget https://www.bloon.io/security/bloon-release-key.gpg
gpg --with-fingerprint --show-keys --keyid-format long bloon-release-key.gpg
It should display the following fingerprint:
C89F 9564 72FB BE40 A5BF 4AA2 F4DF 8C43 B4BB 8D49
Please note that the GPG key URL for BLOON comes from the official website, www.bloon.io. We have also published the fingerprint on our GitHub page. You can cross-reference these sources to confirm that the public key C89F956472FBBE40A5BF4AA2F4DF8C43B4BB8D49 (i.e., the public key fingerprint of bloon-release-key.gpg) is indeed owned by LEXIPON CO., LTD.
Yes! Please trust us! If you have any questions regarding the above explanation, feel free to contact us via support@bloon.io, support@lexipon.com, or through the email addresses of any member of the bloon-io organization on GitHub (you may need to log in to GitHub to see member emails).
If you use BLOON to manage a large number of files, you may need to increase the system's file watch limit. Otherwise, you might encounter issues where file modifications do not sync correctly. You can use the following command to increase the file watch limit:
echo fs.inotify.max_user_watches=500000 | sudo tee -a /etc/sysctl.conf; sudo sysctl -p
The above is a single command; please execute it as one line.
The methods described below will remove the BLOON application itself but will not delete BLOON user data. If you need to completely remove BLOON, manually delete the ~/.bloon folder under each Linux account that has run BLOON.
If you installed BLOON using the DEB package, you can use the following command to uninstall BLOON:
sudo dpkg -P bloon
The -P parameter in the dpkg command is equivalent to --purge, which intends to "completely remove all configuration files and user data of BLOON". However, we do not delete BLOON user data in this command; you still need to manually delete the ~/.bloon folder in each Linux account that has run BLOON.
If you installed BLOON using the RPM package and your system uses DNF to manage packages, you can use the following command to uninstall BLOON:
sudo dnf remove bloon
If your system is openSUSE, you can use the following command to uninstall BLOON:
sudo zypper remove bloon
If you installed BLOON using the script, you can use the following method to uninstall BLOON:
/opt/BLOON/bloon-uninstall.sh
