almalinux / wiki

The AlmaLinux project documentation.

About AlmaLinux Wiki

AlmaLinux is an Open Source and forever-free enterprise Linux distribution, governed and driven by the community, focused on long-term stability and a robust production grade platform. AlmaLinux OS is binary compatible with RHEL®. The AlmaLinux OS Foundation was established as a 501(c)(6) non-profit to steward ownership and governance of the project. The foundation includes over 400 individual members, over 100 Mirror sponsors, and over 25 Corporate sponsors.

Quick Links & Resources

• almalinux.org - Official Web Site
• blog.almalinux.org - Blog
• forums.almalinux.org - Forums
• bugs.almalinux.org - Bug Tracker
• build.almalinux.org - Build System
• lists.almalinux.org - Mailing Lists
• chat.almalinux.org - Mattermost Community Chat
• Libera Chat IRC - IRC Real Time Chat
• reddit.com/r/AlmaLinux - Reddit Community
• repo.almalinux.org - Public Package Repository
• status.almalinux.org - Public Status Page
• Cloud Images (and Sources) for AWS, Google Cloud, Generic/Cloud-Init, LXC/LXD
• AlmaLinux Cloud Images
• Expanded documentation on AWS
• Expanded documentation on Generic Cloud/Cloud-Init
• Container Images:
  • hub.docker.com/_/almalinux - AlmaLinux official images on Docker Hub
  • quay.io/repository/almalinux/almalinux - AlmaLinux official images on Quay.io
• Vagrant Boxes:
  • app.vagrantup.com/almalinux - AlmaLinux on Vagrant Cloud

Transparency Statement

• We are community-owned, which requires transparency. Here is our progress toward that goal.
• Minutes from the meetings of the board of directors

License

This Wiki content is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

wiki's Issues

Document ELevate migration for disconnected environments

It's an often situation when nodes don't have direct Internet access and rely on local mirror for receiving updates.
We need to document migration for such scenarios.
It may be called ELevate Offline Guide or something like that and contain the following information:

1. Creating of AlmaLinux mirror - based on steps 1-3 from https://wiki.almalinux.org/Mirrors.html
2. Creating of ELevate mirror - pretty the same but rsync URL is rsync://rsync.repo.almalinux.org/almalinux-elevate/
3. Adding local ELevate mirror to server (repo file)
4. Installing ELevate
5. Updating leapp configuration (basically replacing mirror server URLs with local mirror URLs)
6. Perform migration

AlmaLinux 9 support period

Hi,
looking at the FAQ page the support of AlmaLinux is listed as until 2029, and links to AlmaLinux 8 announcement.

• Does that apply to both AL 7 & 8?
• Or does the FAQ page need to be updated?
• Is there a better source of support commitment information?

wiki/docs/FAQ.md

Lines 73 to 77 in d422478

	### How long will CloudLinux support AlmaLinux?
	CloudLinux is committed to supporting AlmaLinux until 2029, including stable
	and thoroughly tested updates and security patches. Read more about CloudLinux
	support in the [CloudLinux announcement](https://blog.cloudlinux.com/announcing-open-sourced-community-driven-rhel-fork-by-cloudlinux).

Rename `Building Packages for AlmaLinux` to `AlmaLinux Package Building Guide`

I propose changing the page https://wiki.almalinux.org/documentation/building-packages-guide.html#building-packages-for-almalinux to be called AlmaLinux Package Building Guide

Proposal: Adding more guides that include information that will require payments to our security documentation

We've got pretty great security guides on the wiki, but it came up during our recent Microsoft meetup that @sej7278 has pretty great guides and helpful scripts that he's put together that we might want to link to. Some of the guides have Tuxcare-specific stuff in them, though. How do we feel about adding links to those? Perhaps we include a caveat that some of the content might require charges?

Add edit this page buttons

Please add edit this page buttons on each page.

This will allow edits to come in for the community to fix things.

Enhancing Main Page of Wiki with Mind Map-style Sitemap

We propose enhancing the main page of the wiki by adding a mind map-style sitemap. This visual representation will provide users with a more intuitive way to navigate through the various sections of the wiki, helping them quickly locate relevant information and improving overall user experience.

Feature Details:

• Integrate a mind map-style sitemap on the main page of the wiki.
• The sitemap will visually represent the hierarchy of sections, categories, and pages within the wiki.
• Each node in the mind map will represent a category or a page, and clicking on a node will take the user directly to the respective content.
• The mind map will be interactive, allowing users to expand and collapse nodes for easier navigation and also understand what is available.

Notes:

We are considering using the markmap extension for markdown, which provides the exact functionality we're looking for. You can see live experiments with it here: Markmap Live Experiment.

Static example (I also like this form, we just could not agree on expanding just one branch (Security Guides) to the leaves level):

The attached picture was created using the following code:

# AlmaLinux Wiki _
## About 
## Contribute _
 - Help AlmaLinux OS _
 - Mirrors
## Development _
- Building Packages Guide _
- Modified Packages (list) _
- Packaging Guideline _
## Documentation _
 - EL 8 Distro Comparison _
 - FAQ
 - Howtos
 - Release Notes _
 ### Security Guides _
 - AlmaLinux Security Central _
 - Errata
- OpenSCAP Guide _
- OpenSCAP Guide for 9 _
- SBOM Guide _
## Installation _
- AlmaLinux Installation Guide _
- AlmaLinux WSL _
- Live Media _
- Raspberry Pi _
- Cloud Images
- Containers
- Repositories
## Migration _
- Migration Guide _
- Elevate Project _
## The Foundation _
- AlmaLinux OS Foundation _
- Election 2022 _
- Google Summer Of Code _
- Special Interest Groups _

Add Vault and 32bit repo info

It would be nice to add information about Vault and 32Bit repo and usage info to repo link would be great.

https://wiki.almalinux.org/repos/

Could you add a forum link ?

Could you add a forum link (https://almalinux.discourse.group) to README.md (or Menu bar), please?

Update mirror docs

We should update this page to include a step that tells folks to apply as a mirror member:

https://wiki.almalinux.org/Mirrors.html

Enumeration error in "Contributing to the AlmaLinux project" doc

Hello everyone 🙂

While browsing through Contributing to the AlmaLinux project documentation page, I noticed the number "3" is missing in the Specific Areas we need help with section.

Enumeration goes like this: 1, 2, 4, 5, 6. I think it was changed in 869a67f

The Using of Generic Cloud Images on local machine guide needs refresh

The initial version of the documentation was created on AlmaLinux OS 8.4 times. Thus, too much things changes on the both sides; AlmaLinux OS and Cloud-init. It makes the documentation is not actual, especially the static networking part.

The documentation should be revised and every steps needs to reproduced on the latest version of AlmaLinux OS.

Add more guidelines how to contribute to documentation

To ease the process of contributing to AlmaLinux Documentation and keep it the same style, it would be nice to have style guides listing and describing existing standards.

Example of the guidelines to collaborate on:
#359

update discourse links

With the migration from almalinux.discourse.group to forums.almalinux.org, the links need to be updated.

No i18n support

There's no way to easily translate this wiki to other languages, maybe we should consider a different solution for that because an international community requires different working patterns to develop in parallel.

better way to verify install media

Hi,
Just downloading Alma Linux for a look-see and going through the verification process.

At https://wiki.almalinux.org/release-notes/8.5.html#installation-instructions
You suggest:

# calculate the downloaded ISO SHA256 checksum
$ sha256sum AlmaLinux-8.5-x86_64-boot.iso
65b3b4c17ce322081e2d743ee420b37b7213f4b14d2ec4f3c4f026d57aa148ec  AlmaLinux-8.5-x86_64-boot.iso

# compare it with expected checksum, it should be the same
$ cat CHECKSUM | grep -E 'SHA256.*AlmaLinux-8.5-x86_64-boot.iso'
SHA256 (AlmaLinux-8.5-x86_64-boot.iso) = 65b3b4c17ce322081e2d743ee420b37b7213f4b14d2ec4f3c4f026d57aa148ec

Which is perfectly good :) but you could use:

$ sha256sum -c CHECKSUM --ignore-missing
AlmaLinux-8.5-x86_64-dvd.iso: OK
sha256sum: WARNING: 17 lines are improperly formatted

which is easier if you're a human :)

Clarification about Oracle binary compat from comparision page

Hi,
I was looking at the comparison page. Oracle Enterprise Linux is listed as Almost*(some divergance in glibc, openssl and other components), but there is reference to source of that information. I'm interested in understanding what the divergence is, and would be very grateful to be pointed toward more information related to it.

Wiki page:
https://github.com/AlmaLinux/wiki/blame/e2d44bb5a347795c1be2f9418db57e5785371f90/docs/Comparison.md#L8

From the OEL release post they claim 100% app compat:

Oracle Linux is a highly performant and secure operating environment that helps accelerate digital transformation. It is supported across hybrid and multicloud deployments. Oracle Linux is 100% application binary compatible with Red Hat Enterprise Linux. [Existing applications](https://www.oracle.com/linux/isvcatalog) in user space will continue to run unmodified on Oracle Linux 8 update 6 with [Unbreakable Enterprise Kernel Release 6 (UEK R6)](https://blogs.oracle.com/linux/announcing-the-unbreakable-enterprise-kernel-release-6-update-2-for-oracle-linux) and applications already certified on previous releases of Red Hat Enterprise Linux 8 or Oracle Linux 8 do not require a certification with this new release.

Thanks

Add a page on the wiki & a table about all of the places chat is available and bridged

Right now it's only briefly mentioned on the wiki landing page--we need to make a simple page (or adjust the landing page) to mention everywhere chat is available/bridged.

We will need to add Matrix once it's setup as well.

@bennyvasquez, do you think this should be a separate page or should we just add it to the landing page?

Add/improve build documentaions

Add/improve build documentaion for specific package or module and its dependencies with some sample would be nice for example build jdk 1.8 and its dependencies or nodejs 14 module

The release note of AlmaLinux 8.3 doesn't exist.

I can find the release notes of 8.3beta, 8.3rc, 8.4beta.
But I can't find the release note of 8.3.

IRC Network change from Freenode to Libera

Hello!

Watching your talk at the OpenSUSE Conference Online 2021 on Youtube now: https://youtu.be/mX5XRI_l-1M?list=PL_AMhvchzBafs77OghDUqlDwrIBl9R5QW

And noticed you might want to change the IRC channel link on the wiki: https://wiki.almalinux.org/ from Freenode to Libera

Proposed Content: Add variant for NVIDIA installation from RPM Fusion

I usually install the akmod-nvidia package from RPMFusion rather than the binary or build one as per the Almalinux system guide in the wiki.

I'm happy to write up a new variant for the RPM Fusion version if its acceptable.

Navigation issues when directly accessing a section in the wiki

Hi, I'm having navigation issues when I directly go into a section of the wiki. So far, I'm seeing that it happens when accessing the mirrors section, but I didn't check whether it happens with other sections.

Steps to reproduce:

1. Open a new tab and go into https://wiki.almalinux.org/Mirrors.html
2. Try to move to another section of the wiki using the navigation menu

Expected result:

The browser takes me to the section of the wiki I clicked on the menu

Actual result:

Although the address bar gets updated, I remain in the mirrors section

In Chrome's dev/inspect panel I can see the following error in the console:

app.2f3c144b.js:12 DOMException: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
    at Object.appendChild (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:47748)
    at d (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:60503)
    at u (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:60240)
    at h (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:60589)
    at C (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:63927)
    at C (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:63862)
    at C (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:63862)
    at C (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:63862)
    at C (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:63862)
    at C (https://wiki.almalinux.org/assets/js/app.2f3c144b.js:12:63862)

I guess that there's something inside the mirror section that bothers Vuepress, see the following related issue

Spelling error on Build System meta

Title reads "Buid System" should read "Build System"

Will attach corrected commit

Relationship between `Fedora`, `CentOS`, `RHEL` and `AlmaLinux`

Convert @carlwgeorge tweeter post into a wiki page

https://chat.almalinux.org/almalinux/pl/imsbb6w5kfgbfm6cw6qskrpbqa

https://twitter.com/carlwgeorge/status/1439724277746573314

SSL Certificate issue - https://chat.almalinux.org

SSL Certificate issue - https://chat.almalinux.org

Add a separate page how to get assistance

Currently, it's unclear how users can get any assistance. Having a separate page dedicated to this that is easy to spot for users could be a good idea. For everyone's convenience, it may be worth mentioning all the discussion spaces and some recommendations.

Also may help with the #341

The pr to collaborate - #361

Azure marketplace link to official image is broken

The following link is broken:

wiki/docs/cloud/Azure.md

Line 25 in 853137c

The [official AlmaLinux OS 8 image](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux) is available via the Azure Marketplace at the link provided.

Should it be this : https://azuremarketplace.microsoft.com/en-us/marketplace/apps/almalinux.almalinux-x86_64?tab=Overview ?

Problem with building the wiki

I cannot build the wiki

% yarn install
➤ YN0000: ┌ Resolution step
➤ YN0002: │ @vue/babel-plugin-jsx@npm:1.1.1 doesn't provide @babel/core (pacf39), requested by @babel/plugin-syntax-jsx
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ yallist@npm:3.1.1 can't be found in the cache and will be fetched f
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched f
➤ YN0013: │ yargs-parser@npm:13.1.2 can't be found in the cache and will be fet
➤ YN0013: │ yargs@npm:13.3.2 can't be found in the cache and will be fetched fr
➤ YN0013: │ zepto@npm:1.2.0 can't be found in the cache and will be fetched fro
➤ YN0000: └ Completed in 0s 861ms
➤ YN0000: ┌ Link step
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0007: │ highlight.js@npm:9.18.5 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:3.30.2 must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.14.7 must be built because it never has been before or the last one failed
➤ YN0007: │ vuepress@npm:1.9.9 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 1s 384ms
➤ YN0000: Done with warnings in 2s 640ms

% yarn docs:dev
/var/home/sandorex/slowmf/ws/almalinux-wiki/.pnp.cjs:23888
      Error.captureStackTrace(firstError);
            ^

Error: vuepress tried to access @vuepress/shared-utils, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

Required package: @vuepress/shared-utils
Required by: vuepress@npm:1.9.9 (via /var/home/sandorex/slowmf/ws/almalinux-wiki/.yarn/unplugged/vuepress-npm-1.9.9-61cbd83bbc/node_modules/vuepress/lib/)

Require stack:
- /var/home/sandorex/slowmf/ws/almalinux-wiki/.yarn/unplugged/vuepress-npm-1.9.9-61cbd83bbc/node_modules/vuepress/lib/checkEnv.js
- /var/home/sandorex/slowmf/ws/almalinux-wiki/.yarn/unplugged/vuepress-npm-1.9.9-61cbd83bbc/node_modules/vuepress/cli.js
    at require$$0.Module._resolveFilename (/var/home/sandorex/slowmf/ws/almalinux-wiki/.pnp.cjs:23888:13)
    at require$$0.Module._load (/var/home/sandorex/slowmf/ws/almalinux-wiki/.pnp.cjs:23738:42)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/var/home/sandorex/slowmf/ws/almalinux-wiki/.yarn/unplugged/vuepress-npm-1.9.9-61cbd83bbc/node_modules/vuepress/lib/checkEnv.js:7:27)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at require$$0.Module._extensions..js (/var/home/sandorex/slowmf/ws/almalinux-wiki/.pnp.cjs:23932:33)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at require$$0.Module._load (/var/home/sandorex/slowmf/ws/almalinux-wiki/.pnp.cjs:23769:14)

Node.js v18.16.0

% node --version
v18.16.0
% npm --version
9.5.1
% yarn --version
3.6.0

I've also tried latest node js and same issue

Add systemd timer instructions for mirrors

https://wiki.almalinux.org/Mirrors.html

Due to some confusion with the crontab line using a %, which behaves differently outside of a cron, we need to add an alternative way to do this via a systemd timer.

Example instances of confusion:

• #275
• https://chat.almalinux.org/almalinux/pl/xo1snp586pyjuju7hi6a9894ph
• https://chat.almalinux.org/almalinux/pl/yzpaztd377rtt89pz4xx84ybdh

Add link and information about https://git.almalinux.org

Gil site link needed to added.

May be a dedicated page about site usage.

touch repo No effect

sudo tee /etc/yum.repos.d/mariadb.repo<<EOF
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.5/rhel8-amd64
module_hotfixes=1
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1
EOF

dnf clean all
dnf makecache
dnf install MariaDB-server

not match

bugs.almalinux.org issues

I have two issues with bugs.almalinux.org, but I can't access bugs.almalinux.org to report them there, so maybe someone from here can take a look.

1. email verifications are being sent via sendgrid, a major spammer and pretty much blocked world-wide. Could you please find a better way to send emails?

2. since the verification email was rejected because it came via sendgrid, I have no way to verify my email address, because even if I put a manual white-list, there is no method to request another verification email.

I'd appreciate your input.

Thank you.

Support i18

Can i do i18 it?
I want to add Chinese to it.

Set up automatic build and deployment

It would be nice to build static content and push it to the gh-pages automatically instead of calling deploy.sh all the time.

There are many solutions for this:

• Travis CI integration as described here
• Vuepress deploy GitHub action
• Create a pipeline in our internal Jenkins

Why not add AlmaLinux 9 and 8 into microsoft official WSL distribution Info json?

Here:
https://github.com/microsoft/WSL/blob/master/distributions/DistributionInfo.json

By Microsoft said:
If the distro partner wants to be included on our storage server, they should reach out and provide an appx.

microsoft/WSL#8634

I am using Windows WSL2, and i want to install AlmaLinux 9 with wsl ,

Adjust navigation - release notes

I think the menu list of releases is getting quite difficult to navigate and won't scale further without usability problems. I also don't think it belongs under 'documentation' as it's not really part of what else is there, and it seems like we're burying the release notes quite a bit. I'd like to suggest a solution.

How it is now:

I think we should leave the most recent versions easily accessible, but group the older version 8 and version 9 release notes together, and then within those group the betas together. I also think the release notes should also be a top-level menu item, just under the home page. Like this:

Cleanup Stale braches

It appears stale branches https://github.com/AlmaLinux/wiki/branches contains Merged changes specific some info, safer to cleanup.

Extra Repositories Additional EPEL Info

The Extra Repositories page does not contain enough info to successfully make use of EPEL (at least in Alma Linux 9). Running dnf install epel-release installs successfully, however some EPEL packages (awscli in my case) will still have dependencies that cannot be properly resolved.

The Fedora EPEL Page notes that there are additional repos that need to be enabled (crb for 9, powertools for 8) before installing epel-release. Once I made sure the crb repo was enabled, I was able to successfully install my packages.

It would be helpful to include these additional requirements on the Alma Extra Repositories page as well. I'm coming from CentOS 7 where requirements were simply a yum install epel-release, so I assumed this was still the case looking at the Alma Extra Repositories page.

Document steps necessary to ELevate from 7 to 9

Leapp was designed for 1-step migrations so after 7->8 migrations it's necessary to prepare system for 8->9 step.
We need to document actions necessary for such 2-step migrations.

Cron job command within the mirrors wiki doesn't seem to work

My cron job crashes with
/bin/sh: (RANDOM\%3500)+1: syntax error: invalid arithmetic operator (error token is "\%3500)+1")
however if I take out the backslash and only leave
sleep $(((RANDOM%3500)+1)) it does seem to work.

Maybe point 3 in the https://wiki.almalinux.org/Mirrors.html page should be changed?