wiremock / wiremock/wiremock-docker
4.0.0-beta images are failing due to wrong JDK version
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
Proposal
At the docker image the JAVA_VERSION=jdk-11.0.24+8 is used. But wiremock has been compiled with a newer version (min. Java 17), so the image is failng with this error: java.lang.UnsupportedClassVersionError
Reproduction steps
Running the doker image failes with following error:
docker run -it --rm -p 8080:8080 --name wiremock wiremock/wiremock:4x-beta
Unable to find image 'wiremock/wiremock:4x-beta' locally
4x-beta: Pulling from wiremock/wiremock
Digest: sha256:7ee0a53c479043425775d7766e63a0ff4f29ad4710551bb3ab62792e25aa15c8
Status: Downloaded newer image for wiremock/wiremock:4x-beta
Error: LinkageError occurred while loading main class wiremock.Run
java.lang.UnsupportedClassVersionError: wiremock/Run has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0
References
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the Docker image configuration that sets JAVA_VERSION, then reproduce the failure with the documented docker run command for wiremock/wiremock:4x-beta. Done means the image uses a Java runtime compatible with the class file version reported for wiremock.Run and starts without UnsupportedClassVersionError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100