-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Hub container does not start when upgrading from 1.3.0 to 1.3.1 java: exec format error #251
Comments
@Christopher87R I cannot reproduce this. On my Windows 11 dev machine and on my ubuntu 22.04 VM, both run the 1.3.1 image without any problem. What is your docker-compose file? |
I removed passwords and personal information. |
@Christopher87R On what CPU platform are you building the image? the error indicates, that the wrong cpu architecture is used (e.g. running a docker image build on aarch64 on a amd64 system) |
It is running on a aarch64 machine but worked wit label 1.3.0 |
Can confirm this is a platform issue! I assume the new image (tag stable) is faulty created |
Please agree to the following
Summary
java: exec format error
System Setup
Steps to Reproduce
Changed hub version from 1.3.0 to 1.3.1 in my docker compose file
Hub Container does not start
Expected Behavior
Start of all containers as it was the case for 1.3.0
Actual Behavior
Hub Container crashes with
exec /opt/java/openjdk/bin/java: exec format error
Reproducibility
Always
Relevant Log Output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: