NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Provide an AlmaLinux-Based Container Image
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Summary
Would it be possible to provide an official AlmaLinux-based image variant for Nginx Proxy Manager, alongside the existing Debian/Ubuntu-based image?
Background
Our vulnerability scans regularly report a significant number of CVEs originating from packages included in the current Debian/Ubuntu base image.
Many of these findings may not be directly exploitable within Nginx Proxy Manager, but they still create challenges during customer cybersecurity reviews. Several of our clients now have strict acceptance policies and may reject container images containing Critical, High, or even Medium-severity CVEs, regardless of whether the affected package or functionality is actively used.
In comparison, two other applications that we maintain currently use an updated AlmaLinux 9.8 base image. At the time of our latest scans, these images reported zero known CVEs. This has made security approval and deployment into restricted customer environments considerably easier.
Requested Enhancement
Please consider one of the following options:
Provide an officially maintained AlmaLinux-based Nginx Proxy Manager image.
Provide a RHEL-compatible image based on AlmaLinux, Rocky Linux, or Red Hat UBI.
Publish documentation or a supported build process for creating a custom Nginx Proxy Manager image using an alternative enterprise Linux base.
The existing Debian-based image could remain the default, while an AlmaLinux or RHEL-compatible image could be published as an optional variant, for example:
jc21/nginx-proxy-manager:latest-almalinux
jc21/nginx-proxy-manager:lts-almalinux
jc21/nginx-proxy-manager:2.15.1-almalinux
Benefits
An enterprise Linux-based image could provide:
Fewer vulnerability findings in common container scanners.
Easier approval by customer cybersecurity teams.
Better alignment with RHEL-based production environments.
Longer and more predictable enterprise package-support lifecycles.
Reduced effort spent documenting and mitigating CVEs inherited from the base image.
Improved suitability for regulated, government, defence, and air-gapped environments.
Additional Context
I understand that vulnerability counts depend on the scanner, package versions, repositories, and the date of the scan. We also recognize that a lower CVE count does not automatically make an image more secure.
However, reducing inherited base-image vulnerabilities would significantly improve the practical deploy ability of Nginx Proxy Manager in organizations with strict vulnerability-management policies.
Thank you for considering this request and for maintaining Nginx Proxy Manager.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or build entry points. Start by locating the existing Debian/Ubuntu container-image build and release configuration, then determine whether an AlmaLinux or other RHEL-compatible variant can support the application. Done means a supported image variant or documented build process, with its maintenance and compatibility requirements made clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100