It's worth looking at the experience of other open source projects. For example, the Jenkins project is moving away from Alpline <https://issues.jenkins-ci.org/browse/JENKINS-55547>. The issue specifically is OpenJDK support moving forward. At this moment, it's not clear that the OpenJDK project will publish Alpine-based images, so the Jenkins project cannot rely on that path. This is also being discussed in the mailing list <https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jenkinsci-dev/9kIJFrk9vRA/S3bcVNzKAAAJ>. It's worth following the conversation there.
Also note that Alpine's reputation of being smallest is not necessarily deserved. Here are some observations from our own research on OpenJDK images: - Red Hat Minimal + OpenJDK = 313 MB - Alpine based OpenJDK = 340 MB - Red Hat based OpenJDK 8 image = 456 MB - Debian based OpenJDK = 839 MB As I keep reiterating, as long as all ONAP images derive from the same base, as they eventually will, the actual size of that base is a non issue and we should be choosing our reference implementation based on other criteria such as community health, stability, security, ongoing maintenance, developer mindshare, etc. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15911): https://lists.onap.org/g/onap-discuss/message/15911 Mute This Topic: https://lists.onap.org/mt/30288909/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
