What is this error message before install? 
I have MySQL on many Debian 12 servers and aaPanel can install too. I not heard a problem with not new Debian 12…
So far I know Mysql 8 doesn’t has support for ARM on Debian 12 …
Ooo, then why not that print? I have Xeon cpu.
if [ “$mysql8” = ‘yes’ ] && [ “$architecture” = ‘aarch64’ ]; then
check_result 1 “Mysql 8 does not support ARM64 yet for Debian please use Ubuntu. Unable to continue”
fi
It should be …
Just comment the lines:
339. if [ “$mysql8” = ‘yes’ ] && [ “$release” = ‘12’ ]; then
340. check_result 1 “Mysql 8 does not support Bookworm yet for Debian Unable to continue”
341. fi
And it might just work…
Doesn’t work as there is no apt support for it. However, one can download generic AArch64/ARM64 compatible binaries that work natively on the latest Debian 12.9.0. It works because glibc2.28 is forward compatible with Debian 12.X. For example:
wget https://dev.mysql.com/get/Downloads/MySQL-8.0/mysql-8.4.4-linux-glibc2.28-aarch64.tar.xz
tar -xvf mysql-8.4.4-linux-glibc2.28-aarch64.tar.xz
sudo mv mysql-8.4.4-linux-glibc2.28-aarch64 /usr/local/mysql
I’ve done this and it works well on Debian 12 on ARM64. Haven’t integrated it with HestiaCP. I could install HestiaCP with no MySQL and no MariaDB; install the Generic MySQL 8.4.4 (as I’ve done above); but then how to tell HestiaCP to use it?
Is it just a matter of setting DB_SYSTEM to include mysql in /usr/local/hestia/hestia.conf and have credentials in /usr/local/hestia/mysql.conf ?
Should this become a feature request to fulfill support of MySQL 8 on AArch64?
And then there are no security updates unless we setup our own apt server
That’s a tall order. My production machines are Intel/AMD64 based. But I am seeing a lot more of these AArch64 96-core systems coming online from VPS providers. Perhaps Debian or some Linux (instead of Oracle Linux) will get official support sooner than later.
That is what I was hoping for
1 Like