Closed GamePlayer-8 closed 9 months ago
Hello, thanks for the report. Is this happening in some virtual environment, or physical HW? Could you post output of cat /proc/cpuinfo | grep 'model name' | head -1
command?
Output: model name : Common KVM processor
It's happening in QEMU with KVM accel enabled.
Log of that Docker container:
Fatal glibc error: CPU does not support x86-64-v2
I see. In that case, I think the best option would be to pass the host CPU configuration to the VM. You can change this even after the VM was created, you just need to reboot it to pick up the changes:
Thanks to this you also get better performance inside of the VM. For more information why is this needed, follow this link: https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level
I understand that the images are not consistent in this requirement, but they all benefit from it if available. Moreover, most of the CPUs today should meet this requirement without a problem.
Good afternoon,
There's an issue with
docker-compose-pgsql.yml
Docker compose file, where inpschiffe/pdns-admin
image, glibc requires a CPU withx86_64-v2
instructions while the rest of containers can run onx86_64-v1
.