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
Add support for suse and sles in packaging/distros
HPE uses SLES in some of our products. It would be helpful to us to be able to generate rpms for SLES. As OpenSUSE is closely aligned to SLES and is a free OS I wanted to add that too.
Describe alternatives you've considered
RHEL tinged rpms can be hacked to work with SLES but I prefer not to do that if possible.
Additional context
I have a fork with Dockerfiles that build in SLES and opensuse. We did some testing of the built rpm on a SLES system.
What tests are suggested/required?
In packing/test-release-packages.sh there is support for apt and yum. I think another section for zypper would need to be added. Same for adding a update-zypper-repo.sh script. Is there anything else needed?
It's worth looking at some recent PRs to add other new targets as well just to see if anything else needs covering.
One other thing to say is make sure the packaging/build.sh script works for the distro as ultimately that's all that gets invoked.
The config for targets is here too: https://github.com/fluent/fluent-bit/blob/master/packaging/build-config.json
Once the new target is in there we can trigger a full build on your PR by labelling it ok-package-test. This is the same workflow then run during a full release build and confirms everything is ok (at least for building).
The only other area you may have to look at is the repo creation side - there are scripts under packaging to create the repos we push to the S3 buckets that are the official releases.
Let me know if you want me to pick it up @jhansonhpe, we're going to open-source our Fluent Do agent (https://fluent.do) which includes all this as well but if you have it ready then quicker.
I like what we have for Dockerfiles so far. Dan Illescas from HPE (@illescad) will be taking over the work for the other changes. I will push for a PR by no later than end of next week. @patrick-stephens is that okay for your timing?
i created a PR for opensuse-leap 15.6 and sles15.7 packaging, link is above. i updated the install.sh for suse support, and tried to follow the other distro examples and the same format for base_url
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.
Activity
patrick-stephens commentedon Sep 12, 2025
That's pretty much it, I've got commercial builds that work fine using the existing packaging system with similar changes.
The other things you will need to do:
install.shscript as well to support zypperI'm happy to review the PR if you send it though, that might be easier then talking about it here.
jhansonhpe commentedon Sep 12, 2025
Thanks. We'll work on those parts and get back next week (I expect).
patrick-stephens commentedon Sep 12, 2025
It's worth looking at some recent PRs to add other new targets as well just to see if anything else needs covering.
One other thing to say is make sure the
packaging/build.shscript works for the distro as ultimately that's all that gets invoked.The config for targets is here too: https://github.com/fluent/fluent-bit/blob/master/packaging/build-config.json
Once the new target is in there we can trigger a full build on your PR by labelling it ok-package-test. This is the same workflow then run during a full release build and confirms everything is ok (at least for building).
The only other area you may have to look at is the repo creation side - there are scripts under
packagingto create the repos we push to the S3 buckets that are the official releases.This is the workflow that makes the staging build we eventually release: https://github.com/fluent/fluent-bit/blob/master/.github/workflows/staging-build.yaml
This is the workflow that then promotes staging to release: https://github.com/fluent/fluent-bit/blob/master/.github/workflows/staging-release.yaml
jhansonhpe commentedon Sep 12, 2025
Thanks again - this looks like a good sample PR #10336 and this commit seems good as well - eaa4692
Right?
cosmo0920 commentedon Sep 17, 2025
No, OpenSUSE requires to use zipper instead of apt or yum/dnf. But the required package names could be similar to RHEL derived distros.
jhansonhpe commentedon Sep 17, 2025
You mean zypper. Yes both the sles and opensuse versions will use that as the package manager. I was referring to the structure and what is changed.
patrick-stephens commentedon Sep 19, 2025
Let me know if you want me to pick it up @jhansonhpe, we're going to open-source our Fluent Do agent (https://fluent.do) which includes all this as well but if you have it ready then quicker.
patrick-stephens commentedon Sep 19, 2025
I've also done a PR which includes links to the PRs for backports and docs for the various RHEL-compatible 10 versions here: #10906
jhansonhpe commentedon Sep 19, 2025
I like what we have for Dockerfiles so far. Dan Illescas from HPE (@illescad) will be taking over the work for the other changes. I will push for a PR by no later than end of next week. @patrick-stephens is that okay for your timing?
patrick-stephens commentedon Sep 19, 2025
Yup
patrick-stephens commentedon Sep 30, 2025
How's it looking @jhansonhpe? I'm just looking at our downstream side with a WIP PR: telemetryforge/agent#3
jhansonhpe commentedon Sep 30, 2025
We had a distraction last week but intend to make a PR this week. Sorry about the delay and thanks for the patience.
illescad commentedon Oct 6, 2025
i created a PR for opensuse-leap 15.6 and sles15.7 packaging, link is above. i updated the install.sh for suse support, and tried to follow the other distro examples and the same format for base_url
eschabell commentedon Oct 21, 2025
This is a dep to the docs PR: fluent/fluent-bit-docs#2103.
github-actions commentedon Feb 19, 2026
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the
exempt-stalelabel.github-actions commentedon Feb 26, 2026
This issue was closed because it has been stalled for 5 days with no activity.