Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-05 22:39:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 116

Updated documentation for OpenSUSE support (#32782)

Browse source 
- Policy and script were previously updated in the following PR. This PR
is to update the related doc.
https://github.com/fleetdm/fleet/pull/32779

---------

Co-authored-by: Brock Walters <153771548+nonpunctual@users.noreply.github.com>
This commit is contained in:
Allen Houchins 2025-09-12 09:43:27 -05:00 committed by GitHub
parent a3e0e9d4a9
commit 9de8a7ec0b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
articles/fleet-desktop-on-fedora-and-debian.md
View file

@ -1,21 +1,21 @@
# Enabling Fleet Desktop on Fedora and Debian
# Enabling Fleet Desktop on Fedora, Debian, and OpenSUSE
[Fleet Desktop](https://fleetdm.com/guides/fleet-desktop) is a menu bar icon available on macOS, Windows, and Linux that gives your end users visibility into the security posture of their machine.
[Fleet Desktop](https://fleetdm.com/guides/fleet-desktop) is a menu bar icon for macOS, Linux, and Windows that gives end users visibility into how their device is managed by Fleet and functions as a self-service portal.
Fedora and Debian do not support tray icons by default and rely on the [appindicator-support](https://extensions.gnome.org/extension/615/appindicator-support/) GNOME extension for enabling tray icons. GNOME extensions prompt the end user to accept the installation.
On Linux systems, Fleet Desktop appears as an icon in the menu bar. Fedora and Debian do not support tray icons by default and rely on the [appindicator-support](https://extensions.gnome.org/extension/615/appindicator-support/) GNOME extension for enabling tray icons. GNOME extensions prompt the end user to accept the installation.
This article aims to explain how admins can enable Fleet Desktop on such Linux distributions by using policy queries paired with script execution.
This article explains how admins can enable Fleet Desktop on Linux by using policy queries paired with script execution.
## Policy and script execution
The policy query defined in [check-fleet-desktop-extension-fedora-debian.yml](https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/linux/policies/check-fleet-desktop-extension-fedora-debian.yml) (from our Dogfood environment) checks if the extension needed for Fleet Desktop is installed and enabled on Fedora and Debian hosts.
The policy query defined in [check-fleet-desktop-extension-enabled.yml](https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/linux/policies/check-fleet-desktop-extension-enabled.yml) (from our Dogfood environment) checks if the extension needed for Fleet Desktop is installed and enabled on Fedora, Debian, and OpenSUSE hosts.
> NOTE: fleetd 1.41.0 is required (the policy query relies on a table added to that version).
Starting in version v4.58.0, Fleet supports running scripts to remediate failing policies (see the [Automatically run scripts](./policy-automation-run-script.md) article for more information). Admins can therefore configure Fleet to run [install-fleet-desktop-required-extension.sh](https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/linux/scripts/install-fleet-desktop-required-extension.sh) on devices where the policy detects the extension is missing ([check-fleet-desktop-extension-fedora-debian.yml](https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/linux/policies/check-fleet-desktop-extension-fedora-debian.yml) contains both the policy and remediation script).
Starting in version v4.58.0, Fleet supports running scripts to remediate failing policies (see the [Automatically run scripts](./policy-automation-run-script.md) article for more information). Admins can therefore configure Fleet to run [install-fleet-desktop-required-extension.sh](https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/linux/scripts/install-fleet-desktop-required-extension.sh) on devices where the policy detects the extension is missing ([check-fleet-desktop-extension-enabled.yml](https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/linux/policies/check-fleet-desktop-extension-enabled.yml) contains both the policy and remediation script).
### End-user experience
Following are screenshots of the end-user experience when Fleet runs the script to install the extension (GNOME requires a prompt for installation of extensions for security purposes).
The screenshots below show the end-user experience when Fleet runs the script to install the extension (GNOME requires a prompt for installation of extensions for security purposes).
<p float="left">
<img src="../website/assets/images/articles/fedora_38_appindicator_extension_prompt-326x434@2x.png" title="Fedora 38" width="300" />
@ -24,7 +24,7 @@ Following are screenshots of the end-user experience when Fleet runs the script
> If the end-user hits `Cancel` instead of `Install` then the extension won't be installed and the policy will continue to fail on the host. Fleet only deploys the script on the first failure of the policy, so the end-user won't be prompted again and again, just once. Admins can still run the script on such hosts manually.
### Tray icon
### Menu bar
After the extension is installed your users will see the Fleet icon on their menu bar:
@ -36,5 +36,5 @@ After the extension is installed your users will see the Fleet icon on their men
<meta name="authorGitHubUsername" value="lucasmrod">
<meta name="authorFullName" value="Lucas Rodriguez">
<meta name="publishedOn" value="2025-04-01">
<meta name="articleTitle" value="Enabling Fleet Desktop on Fedora and Debian">
<meta name="articleTitle" value="Enabling Fleet Desktop on Fedora, Debian, and OpenSUSE">
<meta name="category" value="guides">