You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# openSUSE and SUSE Linux Enterprise Server (SLES)
2
2
3
-
Fluent Bit is distributed as the `fluent-bit` package and is available for the latest stable opensuse-leap and sles 15.7 system.
3
+
Fluent Bit is distributed as the `fluent-bit` package and is available for OpenSUSE-Leap 15.6 and SLES 15.7 systems.
4
4
5
5
Fluent Bit supports the following architectures:
6
6
7
7
-`x86_64`
8
8
-`aarch64`
9
9
-`arm64v8`
10
10
11
-
For openSUSE 15, Fluent Bit uses [openSUSE Leap](https://get.opensuse.org/leap) as the canonical base system.
11
+
Fluent Bit supports the following distro versions:
12
+
13
+
- opensuse/leap:15.6
14
+
- sles/15.7
15
+
16
+
For openSUSE, Fluent Bit uses [openSUSE Leap Base Container Images (BCI)](https://build.opensuse.org/project/show/openSUSE:Containers:Leap) as the canonical base system.
17
+
18
+
For SLES, Fluent Bit uses [SUSE Base Container Images (BCI)](https://www.suse.com/products/base-container-images/) as the canonical base system.
12
19
13
20
The recommended secure deployment approach is to use the following instructions:
14
21
15
-
## For openSUSE and SUSE Linux Enterprise Server (SLES)
22
+
## Ensure you select the correct openSUSE verse SLES Package
23
+
24
+
The openSUSE package is built and tested specifically for openSUSE Leap environments, ensuring compatibility with openSUSE libraries, update cycles, and system dependencies. Using the openSUSE package on openSUSE Leap systems helps avoid potential issues with mismatched dependencies or unsupported features that may arise from using SLES packages.
25
+
26
+
The SLES package is tailored for SUSE Linux Enterprise Server and is built against the SUSE Base Container Image, which may include different versions of libraries. It uses enterprise repositories with specific package versions, while Leap uses free, community driven repositories that have a broader range of packages. Installing the SLES package on openSUSE Leap is not recommended, as it may lead to library incompatibilities.
27
+
28
+
29
+
**In summary:**
30
+
- Use the openSUSE package for openSUSE Leap systems.
31
+
- Use the SLES package for SUSE Linux Enterprise Server systems.
16
32
17
-
Fluent Bit provides packages for openSUSE (Leap) and SUSE Linux Enterprise Server (SLES). The repository uses the $releasever variable to dynamically fetch packages for your specific system version.
33
+
This ensures you receive the correct updates and compatibility for your chosen platform.
18
34
19
-
## Configure `zypper`
20
35
21
-
The `fluent-bit` openSUSE package is provided through a `zypper` repository. To add the repository reference to your system:
36
+
## openSUSE Leap
37
+
38
+
Ensure your system repositories are up to date. For openSUSE Leap, use the following repository path:
1. Refresh the repository to make the new packages available.
36
-
```text
37
-
sudo zypper refresh
38
-
```
39
-
1. As a best practice, gpgcheck and repo_gpgcheck are enabled by default for security reasons. Fluent Bit signs its repository metadata and all Fluent Bit packages
40
-
41
-
## Install
42
-
43
-
Ensure you've configured an appropriate mirror. For example:
44
-
45
-
```shell
46
-
$ sed -i 's/mirrorlist/#mirrorlist/g' /etc/yum.repos.d/CentOS-*&& \
47
-
48
-
$ sed -i 's|#baseurl=http://mirror.centos.org|baseurl=http://vault.centos.org|g' /etc/yum.repos.d/CentOS-*
49
-
```
50
-
51
-
An alternative is to use Rocky or Alma Linux, which should be equivalent.
52
56
53
-
## SLES
57
+
1. As a best practice, enable `gpgcheck` for security reasons. Fluent Bit signs its repository metadata and all Fluent Bit packages.
54
58
55
-
For openSUSE and SUSE Linux Enterprise Server (SLES)
59
+
##SUSE Linux Enterprise Server (SLES)
56
60
57
-
Fluent Bit provides packages for openSUSE (Leap) and SUSE Linux Enterprise Server (SLES). The repository uses the $releasever variable to dynamically fetch packages for your specific system version.
61
+
Ensure your system repositories are up to date. For SLES, use the following repository path:
58
62
59
-
## Configure `zypper`
63
+
-`https://packages.fluentbit.io/sles/$releasever`
60
64
61
-
The`fluent-bit` package is provided through a Yum repository. To add the repository reference to your system:
65
+
### Configure Zypper for SLES
62
66
63
-
1. In `/etc/yum.repos.d/`, add a new file called `fluent-bit.repo`.
67
+
1. In `/etc/zypp/repos.d/`, add a new file called `fluent-bit.repo`.
1. As a best practice, enable `gpgcheck`and `repo_gpgcheck`for security reasons. Fluent Bit signs its repository metadata and all Fluent Bit packages.
80
+
1. As a best practice, enable `gpgcheck` for security reasons. Fluent Bit signs its repository metadata and all Fluent Bit packages.
77
81
78
-
### Install
82
+
### Install Fluent Bit
79
83
80
84
1. Ensure your [GPG key](../linux.md#gpg-key-updates) is up to date.
81
85
82
86
1. After your repository is configured, run the following command to install it:
83
87
84
88
```shell
85
-
sudo dnf install fluent-bit
89
+
sudo zypper refresh
90
+
sudo zypper install fluent-bit
86
91
```
87
92
88
93
1. Instruct `Systemd` to enable the service:
@@ -105,36 +110,28 @@ $ systemctl status fluent-bit
105
110
...
106
111
```
107
112
108
-
The default Fluent Bit configuration collect metrics of CPU usage and sends the records to the standard output. You can see the outgoing data in your `/var/log/messages` file.
113
+
The default Fluent Bit configuration collects metrics of CPU usage and sends the records to the standard output. You can see the outgoing data in your `/var/log/messages` file.
109
114
110
115
## FAQ
111
116
112
-
### Yum install fails with a `404 - Page not found` error for the package mirror
117
+
### Zypper install fails with a `404 - Page not found` error for the package mirror
118
+
119
+
Ensure you use the correct `$releaserver` (e.g., `15.6`) in your repo path:
113
120
114
-
The `fluent-bit.repo` file for the latest installations of Fluent Bit uses a `$releasever` variable to determine the correct version of the package to install to your system:
Depending on your Red Hat distribution version, this variable can return a value other than the OS major release version (for example, RHEL7 Server distributions return `7Server` instead of `7`). The Fluent Bit package URL uses the major OS release version, so any other value here will cause a 404.
123
-
124
-
To resolve this issue, replace the `$releasever` variable with your system's OS major release version. For example:
### Yum install fails with incompatible dependencies using CentOS 9+
133
+
zypper knows about special variables like $releasever. It has its own internal logic to replace these with the correct values from your system's baseproduct file.
137
134
138
-
CentOS 9 and later will no longer be compatible with RHEL 9 as it might track more recent dependencies. Alternative AlmaLinux and RockyLinux repositories are available.
135
+
### Zypper install fails with incompatible dependencies
139
136
140
-
See the previous guidance.
137
+
OpenSUSE may track more recent dependencies than SLES. If you encounter dependency issues, ensure you are using the correct repository path for your OS distro.
0 commit comments