OpenLiberty / OpenLiberty/ci.docker
Clarification how images are being released.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 48
- Forks
- 60
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 3
Description
Open Liberty´s documentation is solid, but it is somewhat lacking in the Docker image area.
For instance, when a new version is released (and a blog post published) and available to download from https://openliberty.io/downloads/#docker it can take weeks for the corresponding Docker image to become available.
If a new release is available for download, I assume automatic builds would produce a new image in a day at least.
Note that I don't expect / require a speedy release, that is what you pay support for, but at least some general information so I don't have to check every day for a new image to have been built.
There is also a guide in https://openliberty.io/guides/containerize.html but it fails to clarify the strategy for how Docker images are produced. For instance:
- What Java versions (8, 11, 14) are supported?
- When will new Java versions be introduced as JVM in the OL image?
- When will old Java versions be removed from Docker images?
- Guidance and explanation of differences between "full", "kernel", "kernel-slim". There are some documentation in this repository, but it might be good for new users to have that re-written for easier consumption in the Docker Open Liberty guide above.
There are also two repos on Docker hub:
which one of the above should be used? What is the difference between them?
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 with the containerize guide, downloads page, and both Docker Hub repositories linked in the issue, then compare them with the existing Docker documentation in this repository. Document the image release process, supported Java versions, image variant differences, and which Docker Hub repository users should choose. Done means the guide answers each listed question without requiring daily checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- devops, documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100