Use at your own risk.
To see our changes compared to official source use this link.
. To see our changes compared to official source use this link
release/2.28-72_1.1...custom/2.28-9972_1.1.0+custom1+1
The patch file that applies all changes to glibc is at this link.
https://github.com/sdwru/glibc-centos-8/blob/custom/2.28-9972_1.1.0%2Bcustom1%2B1/SOURCES/glibc-port-2-6-32-kernel-compat.patch
Glibc RPM packages for this release were compiled from the following branch:
https://github.com/sdwru/glibc-centos-8/tree/custom/2.28-9972_1.1.0+custom1+1
Iptables RPM packages for this release were compiled from the following branch. No code changes were made. I simply included the required legacy files the developers chose to disable.
https://github.com/sdwru/iptables-centos-8/tree/custom/1.8.4-1099.0+custom1+1
Systemd RPM packages for this release were compiled from the following branch. This is a very minor change to prevent CE8 from hanging on shutdown/reboot. This might be a systemd bug that will eventually be fixed in an official update and not necessarily directly related to OVZ 6.
https://github.com/sdwru/systemd-centos-8/tree/239-9918_1.4.0+custom1+1
The master and release/. branches track the official upstream source and can be used to see changes when comparing to the custom/. branches. Custom branches will be created as needed.
Versioning
Versioning tracks official source versioning. For official glibc v2.28-42.1, a custom version of 2.28-9942.1.0 is used to ensure official version updates (like an update to v2.28-43, for example) would never be seen as newer and therefore would never install over top of the custom version when doing an update. This would not prevent an official major version bump to v2.29 from being installed and breaking the server. To be absolutely sure the server never breaks it is recommended that you block all future glibc updates by adding exclude=glibc to /etc/dnf/dnf.conf.
Compiled RPM packages are included as a local repository in the OVZ 6 template and also in separate zip files. It is possible to upgrade a running Centos 7 container to Centos 8 using these packages in a local repository using a standard CE7 to CE8 upgrade procedure. That is basically how we created this template.
OpenSSH issue
Openssh-server-8.0p1-4 does not work with OpenVZ 6 kernel.
https://bugzilla.redhat.com/show_bug.cgi?id=1812120
Use openssh-server-8.0p1-5 or openssh-8.0p1-3 instead.
dnf install centos-release-stream
dnf update openssh
How to create a simple local RPM repository
This is already done for you on the OVZ 6 template
yum install createrepo
mkdir -p /opt/packages
cp /home/someusername/rpmbuild/RPMS/*.* /opt/packages
cp /home/someusername/rmpbuild/SRPMS/*.* /opt/packages
createrepo /opt/packages
cat >> /etc/yum.repos.d/local.repo << EOF
[local]
name= Local Packages - x86_64
metadata_expire=-1
gpgcheck=0
enabled=1
baseurl=file:///opt/packages/
EOF