`jdk-community`, `graalvm-community`, and `native-image-community` are essentially the same Docker Image
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 190
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Out of curiosity, I'm wondering if jdk-community, graalvm-community, and native-image-community are essentially the same Docker image?
After all, graalvm ce itself has a command-line tool for native-image. From this perspective, it seems unnecessary to have three image names.
Contributor guide
No contributing guide indexed for this repository
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 comparing the jdk-community, graalvm-community, and native-image-community Docker images with GraalVM CE's native-image command-line tool. Confirm whether they duplicate one another and define which image names should remain; the issue is complete when the relationship and consolidation decision are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100