Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal glibc error: CPU does not support x86-64-v2 #212

Closed
wonx opened this issue Nov 15, 2023 · 5 comments
Closed

Fatal glibc error: CPU does not support x86-64-v2 #212

wonx opened this issue Nov 15, 2023 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@wonx
Copy link

wonx commented Nov 15, 2023

Describe the bug
Since version 1.4.3, I get this error when running gameyfind from a docker container. In my case, docker runs in a virtual machine, running on proxmox. It seems to be incompatible with the default cpu used in proxmox, which is kvm64. Version 1.4.1 works just fine

To Reproduce
Steps to reproduce the behavior:

  1. Use the docker compose script with the image: grimsi/gameyfin:latest
  2. Run the docker container

Expected behavior
Gameyfin should launch.

General info (please complete the following information):

  • Installation method: Docker running inside Debian Buster virtual machine
  • Gameyfin version: v1.4.3
@wonx wonx added the bug Something isn't working label Nov 15, 2023
@grimsi
Copy link
Member

grimsi commented Nov 16, 2023

Looks like youre using an older CPU.

In v1.4.3 the Docker base image for Gameyfin was switched from openjdk:18 to eclipse-temurin:21-jre-ubi9-minimal.
The reason for the switch was the deprecation of the openjdk image.
According to the documentation the new base image supports the following CPU architectures:
amd64, arm32v7, arm64v8, ppc64le, s390x, windows-amd64

Here is a bit more info from the Docker documentation itself: https://github.com/docker-library/official-images#architectures-other-than-amd64

It looks like there are other projects experiencing the same issue due to using a Universal Redhat base image (ubi-minimal): minio/minio#18365 (comment)

So there are currently three solutions (in my order of preference with 1. being the preferred solution):

  1. Switch the base image for Gameyfin again
  2. Build another tag with a different base image specifically for older CPUs
  3. Officially drop support for older CPUs

However I have to research which base image to switch to so that I wont run into similiar issues in the future again.
If you can support me here (by trying out different base images yourself) that would be great since my time is very limited at the moment.

@grimsi grimsi self-assigned this Nov 26, 2023
@Millio345
Copy link

Millio345 commented Dec 30, 2023

I'm having the same issue. Tried a few images that were linked from "openjdk" depreciation notice and "sapmachine:lts-jre-ubuntu-22.04" seems to work. I have no experience with java development so no clue if this is an appropriate image, feel free to ask if you want me to test something else.

I only tested that it boots and the web ui loads, which it does, have not tested anything else.

@grimsi
Copy link
Member

grimsi commented Jan 2, 2024

Thanks a lot! I will take another look at a suitable replacement image. The next release will be using the new image.

Edit: @Millio345 does eclipse-temurin:21-jre-alpine work for you as base image? I would like to keep Temurin since I use it for development.

@Millio345
Copy link

Edit: @Millio345 does eclipse-temurin:21-jre-alpine work for you as base image? I would like to keep Temurin since I use it for development.

I can confirm the eclipse-temurin:21-jre-alpine base image works!

@grimsi
Copy link
Member

grimsi commented Jan 15, 2024

Great, I will switch over to Termurin then with the next release

grimsi added a commit that referenced this issue Jan 28, 2024
@grimsi grimsi closed this as completed Jan 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants