Fatal error with MySQL on secondary server

I manage 2 offices running BlueCherry. I recently fixed an error at the Primary office, but now am having a frustrating issue at the secondary office.

MySql service is restarting every 10 seconds or so. It is the only docker container running, and has the only MySQL server in that office.

Output of ‘docker compose logs bc-mysql’:
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2
bc-mysql | Fatal glibc error: CPU does not support x86-64-v2

Are you using Proxmox? Change the CPU to “host”.

Also…I know the docker version might be appealing…but please use the package versions for mission critical setups.

I use Proxmox at home only. This is setup at work. It is on a bare metal system running Debian Bookworm.

Any other ideas?
Proxmox is not used at this location. Bare metal install on Debian 12. I have only ssh access to this site. Physical access is very seldom.

Can anyone advise if this issue can be triaged as-is, or do we need a newer machine?

Currently, I only have ssh access. I can make a special trip down there if needed. I just would like to know what to tell the bosses?

Current OS is Debian 12 “bookworm”. Unless the normal install has added support, I am unable to install bluecherry.

We should have Debian 12 packages ready for testing in the next week. As I mentioned earlier in the post docker isn’t recommended for production so once the Debian 12 packages are ready you should run ‘docker compose stop’ and ‘docker compose down’ then install the packages

What preparatory procedures will I need to perform in order to migrate from Docker to a “normal” install?

I tried to backup the config to a local computer via the database backup option, but no matter how many I input the 100% correct password for the bluecherry database user, it gives an authentication error.

I was able to dump the bluecherry database with mysqldump (with the EXACT SAME password, mind you) running via docker exec, and piping the output through tee to a file on the docker host system. I’m not sure if that helps in my endeavor or is needed?

The actual recordings are stored on a separate internal HDD I don’t expect to have issues reestablishing the recordings.

Just a point of curiosity: What are the system requirements to run BlueCherry?

The machine at the secondary location has a Core2Duo E7500 CPU, with 4 GB RAM (2x 2GB), running with 3 cameras (4th camera is disabled, due to a hungry rodent and a now broken interface cable)